Enhanced image capture and analysis of damaged tangible objects

ABSTRACT

Apparatuses, systems, and methods are provided for the usage of enhanced pictures (e.g., photos) of tangible objects (e.g., property, cars, etc.) damaged in an accident and answers to questions about the accident to better assess the effect of the damage (e.g., repair expenses and accompanying changes to an insurance policy). A pre-FNOL system may receive responses to one or more questions regarding an accident and one or more enhanced pictures of the tangible property damaged in the accident. The pre-FNOL system may use the responses to the one or more questions and the one or more enhanced pictures to determine repair costs associated with the damaged property and accompanying changes to the insurance policy if an insurance claim were to be filed to cover the determined repairs costs.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/271,812, filed Sep. 21, 2016, the contents of which is incorporatedherein in its entirety by reference.

TECHNICAL FIELD

Aspects described herein generally relate to systems and methods relatedto the usage of enhanced pictures (e.g., photos) of tangible objects(e.g., property, cars, etc.) damaged in an accident and answers toquestions about the accident to better assess the effect of the damage(e.g., repair expenses and accompanying changes to an insurance policy).

BACKGROUND

When an insured item of property is damaged or destroyed during anadverse event, insurance policy holders may take advantage ofconventional claims processing procedures to determine if they willreceive compensation for their losses. While such conventional claimsprocessing procedures are an industry standard in determining losscompensation, insurance policy holders have traditionally had very fewoptions for quantifying the effect on their insurance policy responsiveto the submission of an insurance claim. Accordingly, insurance policyholders often wonder about the amount of damage and whether filing aclaim will adversely impact their insurance policy (e.g., result inhigher premiums or dropped coverage) regardless of whether or notcompensation is awarded to cover the cost of repairing the damages totheir insured property. Thus, there may be a need for calculating damagecompensation and associated effects to an insurance policy prior to thesubmission of an insurance claim.

BRIEF SUMMARY

The following presents a simplified summary of various aspects describedherein. This summary is not an extensive overview, and is not intendedto identify key or critical elements or to delineate the scope of theclaims. The following summary merely presents some concepts in asimplified form as an introductory prelude to the more detaileddescription provided below.

Aspects of the disclosure involve a streamlined and efficient processfor pre-FNOL loss assessment and disclose methods, systems, andapparatuses for determining repair costs for insured property damaged inan accident and accompanying insurance policy changes associated withfiling a claim to cover to the repair costs. A pre-FNOL system mayreceive an indication that insured property was damaged in an accident.In response to receiving the indication, the pre-FNOL system may providequestions regarding the accident to a mobile device associated with theowner of the insured property. Upon receiving answers to the questions,the pre-FNOL system may prompt the owner of the insured property toprovide pictures of the damages to the property. Through analysis of theresponses to the questions and the pictures of the damages, the pre-FNOLsystem may determine repair costs for the damages to the insuredproperty and accompanying insurance policy changes associated withfiling a claim to cover the repair costs.

In another aspect of the disclosure, the pre-FNOL system may receive anindication from the owner of the insured property that the owner wouldlike to file a claim to cover the determined repair costs. Responsive toreceiving such an indication, the pre-FNOL system may deposit a paymentcorresponding to the determined repair costs into a payment accountassociated with the owner of the property.

In another aspect of the disclosure, the pre-FNOL system may receive anindication from the owner of the insured property that the owner wouldnot like to file a claim to cover the determined repair costs, but wouldlike to receive assistance in getting the insured property repaired.Responsive to receiving such an indication, the pre-FNOL system mayprovide information regarding the accident to a repair clearinghouse.Through the repair clearinghouse, the pre-FNOL system may facilitate arepair agreement between the owner of the damaged property and a repairshop. Upon facilitating the repair agreement, the pre-FNOL system mayprovide the owner of the damaged property with repair updates associatedwith repairs performed on the damaged property.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of aspects described herein and theadvantages thereof may be acquired by referring to the followingdescription in consideration of the accompanying drawings, in which likereference numbers indicate like features, and wherein:

FIG. 1 illustrates a pre-FNOL loss assessment system according to one ormore aspects of the present disclosure.

FIG. 2 depicts an initial flow chart for a pre-FNOL loss assessmentmethod according to one or more aspects of the present disclosure.

FIG. 3 depicts a high accuracy flow chart for the pre-FNOL lossassessment method of FIG. 2 according to one or more aspects of thepresent disclosure.

FIG. 4 depicts a low accuracy flow chart for the pre-FNOL lossassessment method of FIG. 2 according to one or more aspects of thepresent disclosure.

FIG. 5A shows a series of initial display screens displayed on a mobilecomputing device when a user commences the high accuracy pre-FNOL lossassessment method according to one or more aspects of the presentdisclosure.

FIG. 5B shows a display screen displayed on a mobile computing device asa user provides details about damages to a vehicle based on the highaccuracy pre-FNOL loss assessment method according to one or moreaspects of the present disclosure.

FIG. 5C shows a series of display screens displayed on a mobilecomputing device for enabling a user to receive feedback from a pre-FNOLloss assessment server based on the high accuracy pre-FNOL lossassessment method according to one or more aspects of the presentdisclosure.

FIG. 6A shows a series of initial display screens displayed on a mobilecomputing device when a user commences the low accuracy pre-FNOL lossassessment method according to one or more aspects of the presentdisclosure.

FIG. 6B shows a series of display screens displayed on a mobilecomputing device for enabling a user to receive feedback from a pre-FNOLloss assessment server based on the low accuracy pre-FNOL lossassessment method according to one or more aspects of the presentdisclosure.

FIG. 7 depicts a flow chart for a pre-FNOL online advisor methodaccording to one or more aspects of the present disclosure.

FIG. 8 depicts a series of display screens displayed on a mobile deviceas a user takes photos of a macro area of a damaged vehicle inaccordance with one or more aspects of the disclosure.

FIG. 9 depicts a series of display screens displayed on a mobile deviceas a user takes photos of a micro area of a damaged vehicle inaccordance with one or more aspects of the disclosure.

FIG. 10 depicts an illustrative operating environment in which variousaspects of the present disclosure may be implemented.

DETAILED DESCRIPTION

In the following description of the various embodiments, reference ismade to the accompanying drawings, which form a part hereof, and inwhich is shown by way of illustration various embodiments in whichaspects described herein may be practiced. It is to be understood thatother embodiments may be utilized and structural and functionalmodifications may be made without departing from the scope of thedescribed aspects and embodiments. Aspects described herein are capableof other embodiments and of being practiced or being carried out invarious ways. Also, it is to be understood that the phraseology andterminology used herein are for the purpose of description and shouldnot be regarded as limiting. Rather, the phrases and terms used hereinare to be given their broadest interpretation and meaning. The use of“including” and “comprising” and variations thereof is meant toencompass the items listed thereafter and equivalents thereof as well asadditional items and equivalents thereof. The use of the terms“mounted,” “connected,” “coupled,” “positioned,” “engaged” and similarterms, is meant to include both direct and indirect mounting,connecting, coupling, positioning and engaging.

FIG. 1 is a diagram illustrating various example components of apre-FNOL loss assessment system 100 according to one or more aspects ofthe disclosure. Pre-FNOL loss assessment system 100 may include avehicle 110, a mobile computing device 120, a network 130, and apre-FNOL system 140. Each component shown in FIG. 1 may be implementedin hardware, software, or a combination of the two. Additionally, eachcomponent of the pre-FNOL loss assessment system 100 may include acomputing device (or system) having some or all of the structuralcomponents described below for computing device 801 as described belowin regards to FIG. 10.

Vehicle 110 of the pre-FNOL loss assessment system 100 may be anautomobile, motorcycle, scooter, bus, van, truck, semi-truck, train,boat, recreational vehicle, or other vehicle. The vehicle 110 mayfurther be an autonomous vehicle, semi-autonomous vehicle, ornon-autonomous vehicle. In some examples, vehicle 110 may includevehicle operation sensors 111 capable of detecting, recording, and/ortransmitting various vehicle performance and/or operational data andenvironmental conditions data. For example, sensors 111 may detect,store, and/or transmit data corresponding to the vehicle's speed, ratesof acceleration and/or deceleration, braking, swerving, and the like.Sensors 111 also may detect, store and/or transmit data received fromthe vehicle's internal systems, such as an impact to the body of thevehicle, air bag deployment, seatbelt usage, and the like.

Sensors 111 also may detect, store, and/or transmit data relating tomoving violations and the observance of traffic signals and signs by thevehicle 110. Additional sensors 111 may detect, store, and/or transmitdata relating to the maintenance of the vehicle 110, such as the enginestatus, oil level, engine coolant temperature, odometer reading, thelevel of fuel in the fuel tank, engine revolutions per minute (RPMs),and/or tire pressure. In some instances, vehicle 110 may include aGlobal Positioning System (GPS) 112 which may be used to detect thevehicle's position and/or location data associated with the vehicle.

Vehicle sensors 111 and GPS 112 may be configured to transmit data toone or more internal computing systems including telematics device 113and/or vehicle on-board computer 115. Additionally, vehicle sensors 111and GPS 112 may be configured to independently transmit theabove-mentioned data to one or more external computing systems includingmobile device 120 and/or pre-FNOL system 140. In some instances, thedata transmission to the one or more external computing systems may beperformed via telematics device 113 and/or vehicle communication system114. In such cases, the vehicle sensors 111 and GPS 112 may beconfigured to transmit data to telematics device 113 and/or vehiclecommunication system 114 which, in turn, may be configured to transmitthe data to the one or more external systems.

Telematics device 113 may be configured to receive vehicle performanceand/or operational data in the form of a data stream from on-boardcomputer 115 via a data port, Bluetooth interface, or any comparablecommunication interface of the vehicle 110. For example, telematicsdevice 113 may include an on-board diagnostic (OBD) device adapter andmay be connected to an OBD port of the vehicle 110. In certainembodiments, telematics device 113 may be configured to receive vehicleperformance and/or operational data directly from vehicle sensors 111,GPS 112, on-board computer 115, and/or mobile device 120 via a wired orwireless connection. Telematics device 113 may include a memory to storedata received from vehicle sensors 111, GPS 112, on-board computer 115,and/or mobile device 120.

In some embodiments, telematics device 113 may store in memory a vehicleidentification number (VIN) of a vehicle 110 associated with aninsurance policy of an insured driver to corroborate vehicle performanceand/or operational data. The VIN associated with vehicle 110 may also bestored in memory associated with on-board computer 115. During operationof vehicle 110, the on-board computer 115 may attach the VIN of vehicle110 to the data stream comprising the vehicle performance and/oroperational data. On-board computer 115 may output the data streamcomprising the VIN and vehicle performance and/or operational data totelematics device 113. Telematics device 113 may corroborate the VINreceived in the data stream from on-board computer 115 to the VIN storedin memory. In doing so, telematics device 113 may determine whether ornot it is operating in the vehicle associated with the insurance policyof the insured driver.

The vehicle performance and/or operational data may be collected withappropriate permissions (e.g., from the driver, vehicle owner, etc.) andmay include operational data from an industry standard port such as aSAE-1962 connector, or an on board diagnostic (“OBD”) port or othervehicle data acquiring component. For example, operation data accessiblevia the OBDII port includes speed and engine throttle position or othervariable power controls of the vehicle power source. It may also includeso called “extended OBDII” or OBDIII datasets that are specific to eachmanufacturer and also available with manufacturer permission such asodometer reading, seat belt status, activation of brakes, degree andduration of steering direction, etc., and implementation of accidentavoidance devices such as turning signals, headlights, seatbelts,activation of automated braking systems (ABS), etc. Other informationregarding the operation of the vehicle may be collected such as, but notlimited to, interior and exterior vehicle temperature, windowdisplacement, exterior vehicle barometric pressure, exhaust pressure,vehicle emissions, turbo blower pressure, turbo charger RPM, vehicle GPSlocation, etc. The system may recognize or be configured to recognize aparticular language emitted by the vehicle system and may configure therecording component to receive or convert data in SAE J1850, ISO IS09141or KWP 2000 formats. Accordingly, U.S. and/or international OBDstandards may be accommodated. For instance, data may be collected froma variety of U.S. and/or international port types to permit use in avariety of locations. Alternatively, this step may be performed by aprocessor after the data is recorded.

Telematics device 113 may also include sensors such as, but not limited,an accelerometer, compass, gyroscope, and GPS system. Telematics device113 may include antennas to communicate with other devices wirelessly.For example, telematics device 113 may communicate with mobile device120 and/or pre-FNOL system 140 over a wide area network (WAN), cellularnetwork, Wi-Fi network, and the like. Telematics device 113 may alsocommunicate with mobile device 120 via a Bluetooth connection. Incertain embodiments, telematics device 113 may be configured toestablish a secure communication link and/or channel with mobile device120 and/or pre-FNOL system 140.

In some arrangements, telematics device 113 may be a telematicsapplication operating on mobile computing device 120 and may utilizehardware components comprised therein (e.g., memory, processors,communication hardware, etc.) to receive, store, and/or transmit vehicleperformance and/or operational data outputted by the on-board computer115. In such an arrangement, telematics device 113 may also utilizesensors included within mobile device 120.

Vehicle communication systems 114 may be implemented using wirelessprotocols such as WLAN communication protocols (e.g., IEEE 802.11),Bluetooth (e.g., IEEE 802.15.1), one or more of the Communication Accessfor Land Mobiles (CALM) wireless communication protocols and airinterfaces, and the like. In certain systems, communication systems 114may include specialized hardware installed in vehicle 110 (e.g.,transceivers, antennas, etc.), while in other examples the communicationsystems 114 may be implemented using existing vehicle hardwarecomponents (e.g., radio and satellite equipment, navigation computers).In some instances, the vehicle communication systems 114 may beconfigured to transmit data provided by vehicle sensors 111, GPS 112,and telematics device 113 to one or more external computing devices overa wide area network (WAN), cellular network, Wi-Fi network, and thelike. Similarly, the communications systems 114 may be configured toreceive data from one or more external computing systems. In someinstances, vehicle communication systems 114 may be configured totransmit data to one or more external computing systems

Vehicle control computer 115 may contain some or all of thehardware/software components as the computing device 801 depicted inFIG. 10, and may be configured to operate aspects of the driving, orother operation of vehicle 110, including but not limited to,acceleration, braking, steering, and/or route navigation. Furthermore,vehicle control computer 115 may be configured to operate one or moreinternal vehicle systems and/or components including at least a vehiclesound system, dashboard display and/or heads-up display system, interiorlighting system, climate control system, door locking systems, and thelike. Similarly, vehicle control computer 115 may be configured tooperate one or more external vehicle systems and/or components includingwindshield wipers, exterior lighting systems (e.g., headlights, taillights, running lights, turn signals, emergency lights, etc.), emissionand exhaust systems, fuel systems, suspension systems, transmissionsystems, and the like. In some instances, vehicle control computer 115may be configured to receive and analyze vehicle performance andoperational data provided by vehicle sensors 111, GPS 112, telematicsdevice 113, and mobile device 120 in order to determine that an accidenthas occurred and to participate in the pre-FNOL procedures described infurther detail below.

In certain embodiments, mobile computing device 120 may be includedwithin the vehicle 110 and may be used to independently collect vehicledriving data and/or to receive vehicle driving data from one or morevehicle systems. Mobile computing device 120 may be, for example, amobile phone, personal digital assistant (PDA), or tablet computer ofthe driver or passenger(s) of vehicle 110. Software applicationsexecuting on mobile computing device 120 may be configured toindependently detect certain driving data. For example, mobile device120 may be equipped with one or more accelerometers and/or GPS systemswhich may be accessed by software applications executing on mobilecomputing device 120 to determine vehicle location, speed, direction,and other basic driving data. As stated above, mobile computing device120 may be configured to transmit the independently collected vehicledriving data and/or the received vehicle driving data and environmentalconditions data to one or more external computing devices (e.g.,pre-FNOL system 140). In other examples, software on mobile computingdevice 120 may be configured to receive some or all of the driving datacollected by vehicle sensors 111 and GPS 112. Mobile computing device120 may also determine that an accident has occurred and participate inthe pre-FNOL procedures described herein.

The pre-FNOL loss assessment system 100 may include a pre-FNOL system140 including a historical data source server 150, a loss assessmentserver 160, and a repair clearinghouse server 170. The pre-FNOL system140 and each of the historical data source server 150, loss assessmentserver 160, and repair clearinghouse server 170 may contain some or allof the hardware/software components as the computing device 801 depictedin FIG. 10.

Historical data source server 150 may comprise a historical data sourcecomputer 152 for receiving and/or processing historical data includinginsurance claims, accident reports, loss assessment profiles, vehicleoperations data associated with insurance claims and accident reports,and the like. The historical data source server 150 may also comprise adatabase 154 used to store the historical data collected by any of thecomputing devices in pre-FNOL loss assessment system 100. In specificregards to the loss assessment profiles, historical data source database154 may store a loss assessment matrix and an accident photo gallery foreach loss assessment profile. In some instances, the loss assessmentmatrices for each of the loss assessment profiles may include vehicledamage costs and insurance policy changes associated with an accident.The historical data source server 150 may be configured to transmit thehistorical data stored in historical data source database 154 to lossassessment server 160, repair clearinghouse server 170, mobile device120, telematics device 113, and/or on-board computer 115 for aiding inthe pre-FNOL procedures described herein.

Loss assessment server 160 may comprise a loss assessment computer 162for receiving, processing, and/or transmitting vehicle operational data,responses to preliminary questions regarding an accident, user vehicleselection information (or vehicle profile information), detailed andgeneral damage information and pictures, and the like. The lossassessment server 160 may also comprise a loss assessment database 164used to store the vehicle operational data, responses to preliminaryquestions regarding an accident, user vehicle selection information (orvehicle profile information), detailed and general damage informationand pictures, and the like received by loss assessment computer 162. Insome instances, the loss assessment database 164 may be configured totemporarily store data received from historical data source server 150and repair clearinghouse server 170. The loss assessment server 160 maybe configured to transmit data stored in loss assessment database 164 tohistorical data source server 150, repair clearinghouse server 170,mobile device 120, telematics device 113 and/or on-board computer 115for aiding in the pre-FNOL procedures described herein.

Loss assessment computer 162 of loss assessment server 160 may be ableto determine, based on the vehicle operational data received fromtelematics device 113, on-board computer 115 via vehicle communicationsystems 114, and/or mobile device 120, that vehicle 110 has beeninvolved in an accident. For example, upon receiving data indicatingthat vehicle 110 has rapidly decelerated from 60 mph to 0 mph withoutalso receiving breaking data, loss assessment computer 162 of lossassessment server 160 may determine that vehicle 110 has been in anaccident. In some instances, loss assessment computer 162 of lossassessment server 160 may be configured to receive an indication from amobile device 120 associated with a driver of vehicle 110 that anaccident has occurred. Such an indication may be a driver-providednotification that vehicle 110 was involved in accident. After receivingdata and/or a user indication that vehicle 110 was involved in anaccident, loss assessment computer 162 of loss assessment server 160 maybe configured to conduct post-accident assistance measures for thedriver of vehicle 110 involved in the accident. As will be discussed infurther detail below, such post-accident assistance measures may includenotifying emergency response personnel that an accident has occurred andproviding the user of mobile device 120 (e.g., the driver of vehicle110) with a post-accident checklist.

Responsive to completing the post-accident assistance measures, lossassessment computer 162 of loss assessment server 160 may be configuredto perform pre-FNOL loss assessment methods in conjunction withhistorical data source server 150 and repair clearinghouse server 170 inorder to determine costs associated with the damages to vehicle 110 andaccompanying changes to an insurance policy associated with vehicle 110if a claim is filed to cover the determined costs of the damages.Aspects of the pre-FNOL loss assessment method performed by lossassessment computer 162 of loss assessment server 160 may includereceiving responses to preliminary questions regarding an accident,determining pre-FNOL loss assessment eligibility based on the responsesto the preliminary questions, performing high accuracy and/or lowaccuracy pre-FNOL loss assessment calculations, and providing payment toa user at the competition of the pre-FNOL loss assessment. In someinstances, loss assessment server 160 may be configured to performpre-FNOL loss assessment methods without conducting post-accidentassistance measures.

Repair clearinghouse server 170 may comprise a repair clearinghousecomputer 172 and repair clearinghouse database 174 to facilitate therepair of vehicle 110 after being involved in an accident. In someinstances, repair clearinghouse database 174 may store data associatedwith repair shops, car rental agencies, and tow truck companies such asprofiles, user ratings, availability schedules, and the like. Repairclearinghouse computer 172 may be configured to provide a sortable listand/or map comprising data corresponding to repair shops, car rentalagencies, and tow truck companies to a driver of vehicle 110. In someinstances, repair clearinghouse computer 172 may be able to consolidatethe repair shop, car rental agency, and tow truck company data presentedto the driver of vehicle 110 based on vehicle location data provided byGPS 112, telematics device 113, and/or mobile computing device 120.Additionally and/or alternatively, repair clearinghouse computer 172 maybe configured to consolidate the repair shop, car rental agency, and towtruck company data presented to the user based on location information(e.g., a zip code) provided by a user and/or associated with aninsurance policy of the user.

The repair clearinghouse computer 172 of repair clearinghouse server 170may be configured to facilitate a repair agreement between a user and arepair shop in instances in which the user does, or does not, file aclaim to cover the determined repair costs. In facilitating the repairagreement, repair clearinghouse computer 172 of repair clearinghouseserver 170 may be configured to provide the information corresponding tothe accident (e.g., vehicle operational data and accident data providedby the driver of vehicle 110 during the pre-FNOL loss assessmentmeasures) to one or more repair shops in the vicinity of the user. Afterproviding the accident information to the one or more repair shops,repair clearinghouse computer 172 of repair clearinghouse server 170 maybe configured to coordinate interactions between the user and the one ormore repair shops to reach a repair agreement. Upon reaching a repairagreement, repair clearinghouse computer 172 may be configured toprovide repair updates associated with the vehicle to the user.

In one example, the repair clearinghouse computer 172 of repairclearinghouse server 170 may create an auction-style platform on whichrepair shops in the vicinity of the user may place bids on the cost ofrepairing vehicle 110 after an accident has occurred based on vehicleoperational data provided by telematics device 113, on-board computer115 via vehicle communication systems 114, and/or mobile device 120, aswell as accident data provided by the driver of vehicle 110 during thepre-FNOL loss assessment measures. The cost of repair bids provided bythe repair shops may be fixed bids (e.g., bids for the exact cost ofrepair) or may be upper-bound bids (e.g., bids for the maximum amountfor the cost of repair). In some instances, the cost of repair bids mayalso include a fixed repair completion time estimate, or an upper-boundcompletion time estimate. A user associated with vehicle 110 may viewthe cost of repair bids provided by the repair shops, the ratings ofeach of the repair shops, and the location each of the repair shops.

The following steps that are described in regards to FIGS. 2-7 may beimplemented by one or more of the components of FIGS. 1 and 8 (describedin detail below) and/or other components, including other computingdevices.

In accordance with aspects of the disclosure, pre-FNOL system 140 mayreceive an indication that vehicle 110 has been in an accident. In someinstances, the indication that an accident has occurred may bedetermined by the loss assessment server 160 of pre-FNOL system 140through analysis of vehicle operational data received from any one, orcombination of, vehicle operation sensors 111, telematics device 113,on-board computer 115 via vehicle communication system 114, and mobilecomputing device 120. In other instances, the indication that anaccident has occurred may be provided by a driver of vehicle 110 via apre-FNOL loss assessment application operating on mobile computingdevice 120 associated with the driver. Alternatively, the indicationthat an accident has occurred may be provided by a driver of vehicle 110through a webpage associated with the pre-FNOL system via mobilecomputing device 120. In some instances, the indication that an accidenthas occurred may be provided by an insurance agent through either apre-FNOL loss assessment application or a webpage associated with thepre-FNOL system 140 and the user inputted information, as describedbelow, may be provided by the insurance agent working on behalf of theuser.

In some embodiments, after receiving an indication of an accident,pre-FNOL system 140 may perform post-accident assistance measures. Thepost-accident assistance measures may include notifying emergencypersonnel that an accident has occurred and providing emergencypersonnel with vehicle information at the time of the accident (e.g.,velocity, seatbelt usage, location data, etc.). In some instances, thepost-accident assistance measures may also include dispatching a towtruck from a tow truck company to the site of the accident and/ordispatching a rental car from a rental car agency to the site of theaccident.

Additionally, the post-accident assistance measures may includeproviding a post-accident checklist to a driver of vehicle 110 through apre-FNOL loss assessment application operating on mobile device 120and/or a webpage associated with the pre-FNOL system 140 being utilizedand/or accessed by mobile device 120. The post-accident check list mayinclude a list of tasks to be performed by a driver of vehicle 110 inorder to be eligible to receive insurance compensation for the accidentand/or be able to be eligible for pre-FNOL loss assessment. Such tasksmay include acquiring insurance information from other drivers of othervehicles involved in the accident, taking photos of areas of vehicle 110damaged in the accident, taking photos of areas of other vehiclesdamaged in the accident, and the like. In some instances, performance ofpost-accident assistance measures may be optional.

Upon completion of the post-accident assistance measures and/orreceiving an indication that an accident has occurred, a user of mobiledevice 120 may provide answers to one or more questions regarding theaccident and one or more pictures associated with damage to vehicle 110.The user may then transmit the answers to the one or more questions andone or more photos to pre-FNOL system 140 for loss assessmentprocessing. Pre-FNOL system 140 may analyze the one or more answersprovided by the user and the one or more photos to determine a cost torepair the damages to vehicle 110 and accompanying insurance policychanges associated with filing a claim to cover the repair costs. Insome instances, pre-FNOL system 140 may incorporate vehicle operationdata received from any one, or combination of, vehicle operation sensors111, telematics device 113, on-board computer 115 via vehiclecommunication system 114, and mobile computing device 120 and historicaldata provided by historical data source server 150 in determining thecost to repair the damages to vehicle 110 and accompanying insurancepolicy changes.

After determining the cost to repair the damages to the vehicle andaccompanying insurance policy changes associated with filing a claim tocover the determined repair costs, the pre-FNOL system 140 may transmitthe determined repair costs and the accompanying insurance policychanges to a mobile device 120 associated with vehicle 110. Subsequentto providing the cost to repair the damages to vehicle 110 andassociated insurance policy changes to be incurred if a claim is filedto, pre-FNOL system 140 may receive an indication from a user of mobiledevice 120 that the user would like to file a claim to cover the cost ofthe damages. After receiving such an indication, the pre-FNOL system 140may deposit payment into a payment account associated with the user forthe calculated repair costs.

In some instances, after providing the repair cost information andassociated insurance policy change data to the user, pre-FNOL system 140may receive an indication from the user of mobile device 120 that theuser would not like to file a claim to cover the cost of the damages,but would instead like assistance in facilitating the repair of thevehicle. After receiving such an indication, the pre-FNOL system 140 maybe configured to provide the information corresponding to the accident(e.g., vehicle operational data and accident data provided by the driverof vehicle 110 during the pre-FNOL loss assessment measures) to one ormore repair shops in the vicinity of the user. After providing theaccident information to the one or more repair shops, pre-FNOL system140 may be configured to facilitate a repair agreement between a userand a repair shop. In facilitating the repair agreement, pre-FNOL system140 may be configured may be configured to coordinate interactionsbetween the user and the one or more repair shops to reach a repairagreement. Upon reaching a repair agreement, repair clearinghousecomputer 172 may be configured to provide repair updates associated withthe vehicle to the user.

Although embodiments of the disclosure discussed herein relate to aninsured vehicle analyzed by pre-FNOL loss assessment system 100, one ofordinary skill in the art would recognize that other types of insureditems, including homes, may be employed with a similar scheme.

FIG. 2 depicts a flow chart for a pre-FNOL loss assessment methodaccording to one or more aspects of the disclosure. In some examples,pre-FNOL loss assessment method may be included in an applicationdownloaded from pre-FNOL system 140 onto a mobile computing deviceassociated with a user. The downloaded application may interface withpre-FNOL system 140 in order to perform the pre-FNOL loss assessmentmethod described herein. Furthermore, such an application may be amulti-functional application and may also include a telematics methodenabling mobile device 120 to receive vehicle operation data fromtelematics device 113 and/or detect vehicle operation data through oneor more sensors (e.g., accelerometer, GPS, etc.) included in mobiledevice 120. Additionally and/or alternatively, the pre-FNOL lossassessment method may be a web-based application performed on pre-FNOLsystem 140. In such instances, mobile device 120 may access a webpageassociated with pre-FNOL system 140 in order to participate in thepre-FNOL loss assessment method described herein.

The method of FIG. 2 may commence at step 202 wherein an indication thatan accident has occurred is received by pre-FNOL system 140. In oneexample, the indication may come in the form of vehicle operational datareceived from telematics device 113, vehicle control computer on-boardcomputer 115 via vehicle communication systems 114, and/or mobile device120. Such vehicle performance data may include each item of vehicle datadescribed herein (e.g., velocity, rates of acceleration and/ordeceleration, braking, swerving, impact to the body of the vehicle, airbag deployment, and the like). When received, the vehicle performancedata may be analyzed by the pre-FNOL system 140 in order to determinethat an accident has occurred. For example, pre-FNOL system 140 mayreceive vehicle operation data indicating that vehicle 110 hasdecelerated from 45 mph to 0 mph with high rotational velocity (e.g.,swerving) and air bag deployment. Such data, when analyzed by pre-FNOLsystem 140, may indicate that vehicle 110 has been involved in anaccident.

Additionally and/or alternatively, the indication may come in the formof a notification from a user associated with mobile device 120indicating that the user was involved in an accident. In some instances,such an indication may come in response to an accident verificationrequest provided by pre-FNOL system 140 to mobile device 120. Forexample, pre-FNOL system 140 may receive vehicle operation datasuggesting that an accident was likely to have occurred. Responsive toreceiving such data, pre-FNOL system 140 may issue an accidentverification request to mobile device 120 in order to confirm that anaccident has indeed occurred. The pre-FNOL system 140 may receive a userresponse to the accident verification request confirming that vehicle110 associated with the user was involved in an accident. In otherinstances, the user notification may be provided by the user of mobiledevice 120 without pre-FNOL system 140 providing an accidentverification request.

In some arrangements, a crash notification may be used to provide anindication that an accident has occurred. For instance, arrangementsdescribed U.S. patent application Ser. No. 14/685,067 entitled,“Automatic Crash Detection” filed on Apr. 4, 2015, with attorney docketno. 006591.00984, which is incorporated herein by reference (and a copyof which is submitted concurrent with the filing of this application inan Information Disclosure Statement), may be used in conjunction withaspects described in the present disclosure to determine that a vehiclehas been involved in an accident.

In one example, after receiving an indication that an accident hasoccurred, pre-FNOL system 140 may provide an alert to emergencypersonnel. The alert may include vehicle operational data received fromtelematics device 113, vehicle control computer on-board computer 115via vehicle communication systems 114, and/or mobile device 120. Suchvehicle operational data may include at least the velocity of thevehicle at the time of the accident, an indication of seat belt use andairbag deployment, and a GPS location associated with the vehicle.Additionally, the pre-FNOL system 140 may also dispatch a tow truckand/or a rental car to the location of the vehicle. In some instances,the dispatch may be performed upon user request.

The pre-FNOL system 140 may additionally provide a post-accidentchecklist to a driver of vehicle 110 through a pre-FNOL loss assessmentapplication operating on mobile device 120 and/or a webpage associatedwith the pre-FNOL system 140 being utilized and/or accessed by mobiledevice 120. The post-accident check list may include a list of tasks tobe performed by a driver of vehicle 110 in order to be eligible toreceive insurance compensation for the accident and/or be able to beeligible for pre-FNOL loss assessment. Such tasks may include acquiringinsurance information from other drivers of other vehicles involved inthe accident, taking photos of areas of vehicle 110 damaged in theaccident, taking photos of areas of other vehicles damaged in theaccident, and the like.

At step 204, pre-FNOL system 140 may provide one or more preliminaryquestions to a driver of vehicle 110 regarding the accident. Suchquestions may be provided through mobile device 120 associated with thedriver of vehicle 110. As shown in screen 502 of FIG. 5A and screen 602of FIG. 6A, the questions (e.g., 502A/602A, 502B/602B, 502C/602C, and502D/602D) may include whether or not there were any injuries to thedriver and/or passengers of vehicle 110 and/or injuries to other partiesinvolved in the accident (e.g., pedestrians, driver and/or passengers ofother vehicles, etc.), whether or not vehicle 110 is driveable, how manyvehicles were damaged in the accident including vehicle 110, and whatlevel of detail of repair costs a user is looking for (e.g., fixed bidor upper-bound bid). In some instances, additional questions may beincluded regarding the geographical location of the accident and type ofaccident (e.g., head-on collision, broadside collision, etc.).

Additionally, the screen 502 may include a field (not shown) throughwhich a user may be able to enter a previously received unique controlnumber from a previously submitted anonymous pre-FNOL loss assessment.Upon entry of such a control number, the pre-FNOL system 140 maypopulate the previously entered data with the information correspondingto the pre-FNOL loss assessment associated with the control number.Responsive to populating the previously entered data, the user may beable to revise the entered data, file a claim, and/or initiate servicesoutside of a traditional claim as described below.

Responsive to providing the preliminary questions, pre-FNOL system 140may receive responses to the one or more preliminary questions from thedriver of vehicle 110 via mobile device 120. Based on the responsesprovided, pre-FNOL system 140 may determine whether or not the driver iseligible for pre-FNOL loss assessment in step 206. For example, if thedriver reports that injuries were sustained in the accident, vehicle 110is no longer driveable, and that three vehicles were involved in theaccident, pre-FNOL system 140 may conclude that pre-FNOL loss assessmentis not applicable. In determining ineligibility, pre-FNOL system 140 mayincorporate data from historical data source server 150. Alternatively,pre-FNOL system 140 may determine ineligibility based upon pre-setcriteria that, if fulfilled, yield a determination of ineligibility. Forexample, pre-set criteria may include an accident in excess of four ormore vehicles wherein there are injuries and vehicle 110 is deemedundriveable. In another example, the pre-set criteria may includewhether or not injuries were sustained in the accident. Such examples ofpre-set criteria are illustrative and other arrangements are possible.

In the event that pre-FNOL system 140 determines that pre-FNOL lossassessment is not applicable, a notification may be provided to mobiledevice 120 in step 208 indicating that the user is ineligible forpre-FNOL loss assessment. The notification may include an indication asto why the user was deemed ineligible (e.g., four or more vehicles wereinvolved in the accident, injuries were reported, and vehicle 110 wasundriveable, etc.) and a suggestion to file a formal claim to assess thedamages incurred during the accident. The notification may also providea login portal through which the user may access an account associatedwith an insurance provider in order to file a formal claim. Uponsuccessful login, the pre-FNOL system 140 may provide the receivedvehicle operation data and the responses to the one or more preliminaryquestions to the insurance provider to aid in the claim filing process.

In the event that the pre-FNOL system 140 determines that pre-FNOL lossassessment is applicable in step 206, pre-FNOL system 140 may thendetermine whether or not the pre-FNOL loss assessment is an anonymous ornon-anonymous loss assessment in step 210. For example, after receivinganswers to the questions put forth in screens 502/602, the pre-FNOL lossassessment system 140 may then provide the user with an option to log into an account associated with an insurance provider of the user. For anon-anonymous pre-FNOL loss assessment, the user may log into anassociated insurance account. For an anonymous pre-FNOL loss assessment,the user may decline the option to log in to an associated insuranceaccount. In such instances, the pre-FNOL system 140 may generate aunique control number associated with the anonymous pre-FNOL lossassessment that identifies the user initiating the anonymous pre-FNOLloss assessment in order to track usage of the pre-FNOL system 140either through the application on mobile device 120 and/or the webapplication being accessed by mobile device 120. Additionally, theunique control number may enable the pre-FNOL system 140 to determinechanges made by the user to the information provided in the anonymouspre-FNOL loss assessment, as well as to convert an existing anonymouspre-FNOL loss assessment to a claim or initiate services in instances inwhich a traditional claim is not filed.

In some instances, step 210 may be performed concurrently with, or priorto, step 206. In one example, the insurance provider account loginportal (e.g., 502E/602E) may be presented to a user with the one or morepreliminary questions shown in screen 502 of FIG. 5A and 602 of FIG. 6A.Upon selection of the insurance provider account log in portal, a pop-upscreen may be presented to the user in order to enable the user toprovide account information (e.g., insurance provider, policy number,username, and password). As such, the determination of whether or notthe pre-FNOL loss assessment is an anonymous or non-anonymous lossassessment may occur prior to receiving the responses to the one or morepreliminary questions. In another example, insurance provider, policynumber, username, and password fields may be presented in-line with theone or more preliminary questions. In such instances, steps 206 and 210may be performed simultaneously upon receipt of the user submission ofthe login information and answers to the one or more preliminaryquestions.

In any case, the pre-FNOL system may either proceed to step 212 andprovide the user with screen 504 as shown in FIG. 5A in the event of anon-anonymous pre-FNOL loss assessment or proceed to step 214 andprovide the user with screen 604 as shown in FIG. 6A in the event of ananonymous pre-FNOL loss assessment.

For the non-anonymous pre-FNOL loss assessment, the user may bepresented with screen 504 depicted in FIG. 5A at step 212. The screen504 may include a vehicle registry and a prompt 504A for the user toselect a vehicle associated with the insurance account of the user thatwas involved in the accident. In the example shown in screen 504, theuser may have two vehicles (e.g., Vehicle A and Vehicle B). Vehicles Aand B may correspond to any of the vehicles discussed herein withrespect to vehicle 110 (e.g., an automobile, motorcycle, scooter, bus,van, truck, semi-truck, train, boat, recreational vehicle, or othervehicle). In particular, the vehicles A and B may denote a specific makeand model of vehicle (e.g., 2010 Toyota® Camry, 2016 Kia® Sorrento,etc.) and may be further associated with the VIN of the vehicle. Theinformation corresponding to vehicles A and B may be previously enteredby a user associated with the insurance account and pre-stored inpre-FNOL system 140. Accordingly, screen 504 may depict as many vehiclesas the user has previously entered.

In some instances, screen 504 may also present a “Not Listed” option foruser selection, which may be appropriate for instances in which the useris involved in an accident while driving a rental vehicle, borrowedvehicle (e.g., from a relative or a friend), company vehicle, and/or avehicle not previously entered by the user. In response to the selectionof “Not Listed”, pre-FNOL system 140 may present the user with a screensimilar to that shown by screen 604 of FIG. 6A wherein the user isrequired to answer questions about the vehicle before pre-FNOLassessment can be conducted.

For the anonymous pre-FNOL loss assessment, the user may be presentedwith screen 604 depicted in FIG. 6A at step 214. The screen 604 mayinclude one or more vehicle profile questions (e.g., 604A, 604B, 604C,604D, and 604E) regarding vehicle 110 including the VIN, which may beoptional, year, make, model, and mileage. As stated above, suchquestions may be similar to those presented to a user conducting anon-anonymous pre-FNOL loss assessment responsive to a selection of the“Not Listed” option shown in screen 504 of FIG. 5A.

Upon receiving either the vehicle selection in step 212 for anon-anonymous pre-FNOL loss assessment or responses to the vehicleprofile questions in step 214 for an anonymous pre-FNOL loss assessment,pre-FNOL system 140 may proceed to step 216 and determine whether theuser has requested a high accuracy pre-FNOL loss assessment (e.g.,accurate anticipated repair cost and/or fixed repair cost) or a lowaccuracy pre-FNOL loss assessment (e.g., less accurate anticipatedrepair cost and/or upper-bound repair cost). A user selection of a highaccuracy pre-FNOL loss assessment is shown in screen 502 of FIG. 5A inresponse to question 502D and a user selection a low accuracy pre-FNOLloss assessment is shown in screen 602 of FIG. 6A in response toquestion 602D.

In some instances, step 216 may be performed concurrently with steps 206and 210. For example, the pre-FNOL system 140 may receive a user'sinsurance login information and the user's answers to the one or morepreliminary questions including what type of repair costs the user islooking for (e.g., 502D/602D). In such instances, steps 206, 210, and216 may be performed simultaneously upon receipt of the user submissionof the login information and answers to the one or more preliminaryquestions.

In the event that the user has selected a high accuracy pre-FNOL lossassessment (e.g., accurate anticipated repair cost and/or fixed repaircost), the pre-FNOL system 140 may proceed to step 302 of the highaccuracy pre-FNOL loss assessment method shown in FIG. 3. In someinstances, the user may not need to be logged in to an account of anassociated insurance provider in order to receive a high accuracypre-FNOL loss assessment. However, in other instances, the user may needto be logged in to an account of an associated insurance provider inorder to receive a high accuracy pre-FNOL loss assessment.

At step 302, the pre-FNOL system 140 may provide the detailed damagedescription screen 506, as shown in FIG. 5B, to a user of vehicle 110regarding the accident. The detailed damage description screen 506 mayinclude a plurality of accordion-type, selectable fields (e.g., 506A,506B, 506C, and 506D) corresponding to macro areas of the vehicle 110that may or may not have been damaged in the accident such as the front,rear, driver side, and passenger side. The selection of one or more ofthe plurality of accordion-type, selectable fields may serve as anindication to pre-FNOL system 140 that the macro area corresponding tothe particular field selected was damaged during the accident.

Upon selection, the accordion-type field may reveal a plurality ofselectable sub-options corresponding to micro damage areas within thelarger, macro location denoted by the accordion-type field itself. Forexample, in regards to accordion-type, selectable field 506Ccorresponding to the driver side of vehicle 110, upon selection, aplurality of additional micro damage areas (e.g., Option 1-Option 9) maybecome available to the user. Each of the micro damage areas maycorrespond to a more specific area within the driver side of the vehicle110 (e.g., driver side front tire, driver side front door, driver siderear door, etc.). In some instances, more than nine options may beavailable to the user for selection and each of the options may belabeled in accordance with the portion of vehicle 110 they represent.Additionally, the options may be labeled according to a reference schemedeveloped by the manufacturer of the vehicle in order to streamlineterminology used during the course of repair.

The options 1-9, when selected by the user, may be labeled on arendering of the vehicle 110, which may be produced at an orientationcorresponding to that of the accordion-type, selectable field. Forexample, when accordion-type, selectable field 506C corresponding to thedriver side of vehicle 110 is selected, a driver side rendering ofvehicle 110 may be produced. In some instances, the renderings of thevehicle may correspond to the vehicle selected by the user in step 212(e.g., Vehicle A or Vehicle B). However, in other instances, therenderings of the vehicle may correspond to a generic vehicle of a classsimilar to that of the vehicle selected by the user in step 212 (e.g.,truck, sedan, coupe, hatchback, etc.).

In one example, the area of the vehicle corresponding to the optionselected is labeled with the number of the option (e.g., 1, 2, 5, etc.).In another example, the area of the vehicle corresponding to the optionselected is highlighted, shaded, outlined, and/or marked in a wayindicating that it corresponds to the option selected.

Additionally and/or alternatively, the options may also beaccordion-type, selectable fields that, when selected by the user,reveal a slidable damage scale associated with the area of the vehiclecorresponding to the option. The slidable damage scale may be linearlydisplaced by the user from a lower bound corresponding to no damage toan upper bound corresponding to severe damage, and the area of thevehicle corresponding to the option may depict a variable degree ofdamage corresponding to the linear displacement of the slidable scale.Through the utilization of the slidable damage scale, a user may be ableto visually perceive damage to specific areas of the vehicle in a mannerquantifiable by pre-FNOL system 140.

In some instances, a user may be required to provide one or morepictures of the areas of the vehicle damaged in the accident. Therequired pictures may correspond to the area of the vehicle denoted bythe accordion-type, selectable fields 506A, 506B, 506C, and/or 506D(e.g., front, rear, driver side, and/or passenger sides of the vehicle)selected by the user as being damaged in the accident. Additionallyand/or alternatively, the required pictures may correspond to the one ormore sub-options (e.g., Option 1-Option 9) selected by the user as beingdamaged by the accident. For instance, in the example shown in screen506 of FIG. 5B wherein the user has selected accordion-type, selectablefield 506C and sub-options 4, 5, and 6, the user may be required to takeone or more photos of the driver side of the vehicle and one or morephotos of the areas denoted 4, 5, and 6 in the rendering of the vehicle.

The pre-FNOL system 140 may be configured to initially process thepictures submitted by the user in order to determine if they are of aquality, size, and shape suitable to perform the pre-FNOL lossassessment methods described herein. In some instances, the pre-FNOLserver 140 may be further configured to analyze the photos provided bythe user to determine whether or not they correspond to the areasidentified by the user selected accordion-type, selectable fields andthe user selected sub-options.

In one example, responsive to receiving a user selection of anaccordion-type, selectable field of the plurality of accordion-type,selectable fields corresponding to a particular macro area of thevehicle (e.g., front, rear, driver side, passenger side), pre-FNOLsystem 140 may activate a camera on mobile device 120 and accompanyinguser interface. As shown in FIG. 8, when activated, the user interfaceassociated with the camera of mobile device 120 may generate asemi-translucent overlay 802C on the viewport 802A of the mobile device.In some instances, the semi-translucent overlay 802C may correspond tothe macro area of the vehicle corresponding to the user selectedaccordion-type field. For example, in the event that the user selectedthe accordion-type, selectable field corresponding to the front of thevehicle, the user interface associated with the camera of mobile device120 may generate a semi-translucent overlay 802C corresponding to thefront of the vehicle. In some instances, the semi-translucent overlay802C may correspond to the vehicle selected by the user in step 212(e.g., Vehicle A or Vehicle B). However, in other instances, thesemi-translucent overlay of the vehicle may correspond to a genericvehicle of a class similar to that of the vehicle selected by the userin step 212 (e.g., truck, sedan, coupe, hatchback, etc.). In oneexample, the semi-translucent overlay may correspond to the outline ofthe vehicle (either the user-selected vehicle or the generic vehicle ofthe class similar to that of the user-selected vehicle) and in anotherexample, the semi-translucent overlay may correspond to the outline ofvehicle with lines denoting the additional structure included therein.Alternatively, the semi-translucent overlay may be a geometric shapesuch as an oval, circle, rectangle, square, and the like.

The semi-translucent overlay may serve as an aide for the user incapturing an image suitable for the pre-FNOL system 140 to conduct thepre-FNOL loss assessment calculations. In some instances, before thepre-FNOL system 140 activates the camera on mobile device 120 and theaccompanying user interface including the semi-translucent overlay, atutorial screen may be presented to the user demonstrating the properuse of the semi-translucent overlay. The tutorial screen may provide theuser with a plurality of user interface screen shots depicting correctand incorrect usages of the semi-translucent overlay. In regards tocorrect usages, the tutorial screen may show a green check markcorresponding to instances in which the semi-translucent overlay isproperly aligned with a vehicle. In regards to incorrect usages, thetutorial screen may show a red ‘X’ corresponding to instances in whichthe semi-translucent overlay is not properly aligned with the vehicle.Through the presentation of the tutorial screen, the user may be able tobetter understand how to use the semi translucent overlay in capturingpictures of the damaged areas of the vehicle suitable for the pre-FNOLsystem 140 to conduct the pre-FNOL loss assessment calculations.

In one example depicted in FIG. 8, after a user has proceeded past thetutorial screen, the camera of mobile device 120 may be activated andthe user interface associated with the camera of mobile device 120 maygenerate a semi-translucent overlay 802C on the viewport 802A of themobile device. The semi-translucent overlay 802C may be semi-opaque and,as such, may allow for viewing of the image data captured by the cameraof the mobile device 120 through the semi-translucent overlay 802C. Asshown in screen 802, the semi-translucent overlay 802C may be generatedin a center portion of viewport 802A. Additionally, image datacorresponding to the vehicle of the user (e.g., 802B) may also bedisplayed in the viewport 802A in instances in which the vehicle is inthe perceptible range of the camera of the mobile device. As shown inscreen 804, as the user of mobile device 120 approaches the damagedvehicle, the image data corresponding to the damaged vehicle of the user(e.g., 804B) may take up more area in the viewport 804A of mobile device120. Conversely, the size of the semi-transparent overlay 804B mayremain fixed compared to the size of the semi-transparent overlay 802Cdepicted in screen 802. Furthermore, as shown in screen 804, the imagedata corresponding to the vehicle of the user (e.g., 804B) may beviewable through the semi-translucent overlay 804C in instances in whichthe semi-translucent overlay 804C and the image data corresponding tothe vehicle are overlapped. As shown in screen 806, the user may be ableto orient the mobile device 120 relative to the user's damaged vehiclein such a way as to cause the image data corresponding to the vehicle ofthe user (e.g., 806B) to be aligned with the semi-translucent overlay806C.

The user may be able to take a photo at any time after the camera ofmobile device 120 is activated and the user interface associated withthe camera of the mobile device 120 generates the semi-translucentoverlay 802C on the viewport 802A of the mobile device. To take thephoto, the user may select the photo button (e.g., 802D/804D/806D) ormay press a physical button on the mobile device typically used to takea photo (e.g., volume button). In some instances, the image data of thephoto captured by the user may correspond to the area within thesemi-transparent overlay. Stated differently, while the entire viewportof the mobile device may show an image corresponding to the image datacaptured by the camera of the mobile device, only the image dataincluded within the semi-translucent overlay is captured and retained(e.g., not discarded) when a photo is taken. As such, thesemi-translucent overlay may serve as an outer boundary for photoscaptured by the user, wherein the outer boundary traces the border ofthe semi-translucent overlay. In other instances, the image data of thephoto captured by the user may correspond to an area larger than thesemi-transparent overlay. The larger area may correspond to a border ofone or more pixels surrounding the semi-transparent overlay. Thus, thedata captured by the photo may include the area of the semi-transparentoverlay in addition to the border of one or more pixels surrounding theoverlay. Alternatively, the image data of the photo captured by the usermay correspond to entire image rendered by the camera of the mobiledevice in the viewport.

After the photo has been taken, mobile device 120 may transmit the datacorresponding to the photo to pre-FNOL system 140 for processing. Ininstances in which the captured image data corresponds to the area ofthe semi-transparent overlay, the pre-FNOL system 140 may analyze theimage data provided by mobile device 120 to determine if the providedimage data corresponds to the area of the vehicle corresponding to thesemi-transparent overlay. For example, the pre-FNOL system 140 maycompare the received image data to one or more stored imagescorresponding to the make and model of the vehicle of the user and themacro area corresponding to the semi-transparent overlay. If thereceived image data is determined to correspond to the one or morestored images, the pre-FNOL system 140 may accept the photo and providenotification to mobile device 120 of the user that the photo wasaccepted. However, if the received image data is determined not tocorrespond to the one or more stored images, the pre-FNOL system 140 maydecline the photo and provide notification to mobile device 120 that aretake of the photo is required.

Similarly, in instances in which the captured image data corresponds tothe area of the semi-transparent overlay in addition to one or morepixels bordering the outline of the semi-transparent overlay, pre-FNOLsystem 140 may analyze the image data provided by mobile device 120 todetermine if the provided image data corresponds to the area of thevehicle corresponding to the semi-transparent overlay. For example, thepre-FNOL system 140 may compare the received image data to one or morestored images corresponding to the make and model of the vehicle of theuser and the macro area corresponding to the semi-transparent overlay.If the received image data is determined to correspond to the one ormore stored images, the pre-FNOL system 140 may accept the photo andprovide notification to mobile device 120 of the user that the photo wasaccepted. However, if the received image data is determined not tocorrespond to the one or more stored images, the pre-FNOL system 140 maydecline the photo and provide notification to mobile device 120 that aretake of the photo is required.

Alternatively, in instances in which the image data of the photocaptured by the user corresponds to the entire image rendered by thecamera of the mobile device in the entire area of the viewport, Thepre-FNOL system 140 may analyze the image data provided by mobile device120 to determine if the provided image data corresponds to the area ofthe vehicle corresponding to the semi-transparent overlay. For example,the pre-FNOL system 140 may compare the received image data to one ormore stored images corresponding to the make and model of the vehicle ofthe user and the macro area corresponding to the semi-transparentoverlay. If the received image data is determined to correspond to theone or more stored images, the pre-FNOL system 140 may accept the photoand provide notification to mobile device 120 of the user that the photowas accepted. However, if the received image data is determined not tocorrespond to the one or more stored images, the pre-FNOL system 140 maydecline the photo and provide notification to mobile device 120 that aretake of the photo is required. In some examples where the capturedimage data corresponds to the entire viewport, the pre-FNOL system 140may, once the appropriate portion of the full image data correspondingto the overlay has been identified (either manually and/or in automatedway), discard the extraneous image data outside of the boundary of theoverlay. As a result, the final image data requires less space andbandwidth than the full image data, in those examples.

In some instances in which the image data of the photo captured by theuser corresponds to the entire image rendered by the camera of themobile device in the entire area of the viewport, mobile device 120 maysubsequently discard data outside of the semi-translucent overlaygenerated on the viewport. Such discarding may either occur at mobiledevice 120 or at pre-FNOL system 140. In either case, the remaining,non-discarded image data may be stored by pre-FNOL system 140 theremaining, non-discarded image data may be smaller in size than thecaptured image data.

Through the utilization of the semi-translucent overlay, the pre-FNOLsystem may create a catalog and/or database of standardized pictures ofspecific sizes and orientations. Such standardization may the improvethe functionality of the pre-FNOL system 140 in performing the pre-FNOLloss assessment measures described herein by increasing processingefficiency and bandwidth, decreasing required processing power, andmaximizing available memory. Furthermore, as will be appreciated by oneof ordinary skill in the art, the performance improvements of pre-FNOLsystem 140 may be further increased in instances in which the capturedimage data corresponds to the area of the semi-transparent overlay andinstances in which the captured image data corresponds to the area ofthe semi-transparent overlay in addition to one or more pixels borderingthe outline of the semi-transparent overlay due to the reduction in sizeof the image files.

Furthermore, pre-FNOL system 140 may generate a similar semi-translucentoverlay for the area of the vehicle corresponding to each of the userselected sub-options within the greater accordion-type, selectablefield. In one example, responsive to receiving a user selection of asub-option corresponding to a particular micro area of the vehiclewithin the larger macro area, pre-FNOL system 140 may activate a cameraon mobile device 120 and accompanying user interface. As shown in FIG.9, when activated, the user interface associated with the camera ofmobile device 120 may generate a semi-translucent overlay 902C on theviewport 902A of the mobile device. In some instances, thesemi-translucent overlay 902C may correspond to the micro area of thevehicle corresponding to the user selected sub-option. For example, inthe event that the user selected the sub-option corresponding to damageto the passenger side headlight, the user interface associated with thecamera of mobile device 120 may generate a semi-translucent overlay 902Ccorresponding to the micro area of the front of the vehiclecorresponding to the passenger side headlight. In some instances, thesemi-translucent overlay 902C may correspond to the vehicle selected bythe user in step 212 (e.g., Vehicle A or Vehicle B). However, in otherinstances, the semi-translucent overlay of the vehicle may correspond toa generic vehicle of a class similar to that of the vehicle selected bythe user in step 212 (e.g., truck, sedan, coupe, hatchback, etc.). Inone example, the semi-translucent overlay may correspond to the outlineof the vehicle (either the user-selected vehicle or the generic vehicleof the class similar to that of the user-selected vehicle) and inanother example, the semi-translucent overlay may correspond to theoutline of vehicle with lines denoting the additional structure includedtherein. Alternatively, the semi-translucent overlay may be a geometricshape such as an oval, circle, rectangle, square, and the like.

In one example depicted in FIG. 9, after user selection of thesub-option, the camera of mobile device 120 may be activated and thegraphical user interface associated with the camera of mobile device 120may generate a semi-translucent overlay 902C on the viewport 902A of themobile device. The semi-translucent overlay 902C may be similar to thesemi-translucent overlay(s) described above in regards to FIG. 8.

As shown in screen 902, the semi-translucent overlay 902C may begenerated in a center portion of viewport 902A. Additionally, image datacorresponding to the vehicle of the user (e.g., 902B) may also bedisplayed in the viewport 902A in instances in which the vehicle is inthe perceptible range of the camera of the mobile device. As shown inscreen 904, as the user of mobile device 120 approaches the damagedvehicle, the image data corresponding to the damaged vehicle of the user(e.g., 904B) may take up more area in the viewport 904A of mobile device120. Conversely, the size of the semi-transparent overlay 904B mayremain fixed compared to the size of the semi-transparent overlay 902Cdepicted in screen 902. Furthermore, as shown in screen 904, the imagedata corresponding to the vehicle of the user (e.g., 904B) may beviewable through the semi-translucent overlay 904C in instances in whichthe semi-translucent overlay 904C and the image data corresponding tothe vehicle are overlapped. As shown in screen 906, the user may be ableto orient the mobile device 120 relative to the user's damaged vehiclein such a way as to cause the image data corresponding to the vehicle ofthe user (e.g., 906B) to be aligned with the semi-translucent overlay906C.

The user may be able to take a photo at any time after the camera ofmobile device 120 is activated and the user interface associated withthe camera of the mobile device 120 generates the semi-translucentoverlay 902C on the viewport 902A of the mobile device. To take thephoto, the user may select the photo button (e.g., 902D/904D/906D) ormay press a physical button on the mobile device typically used to takea photo (e.g., volume button). In some instances, the image data of thephoto captured by the user may correspond to the area within thesemi-transparent overlay. Stated differently, while the entire viewportof the mobile device may show an image corresponding to the image datacaptured by the camera of the mobile device, only the image dataincluded within the semi-translucent overlay is captured when a photo istaken. In other instances, the image data of the photo captured by theuser may correspond to an area larger than the semi-transparent overlay.The larger area may correspond to a border of one or more pixelssurrounding the semi-transparent overlay. Thus, the data captured by thephoto may include the area of the semi-transparent overlay in additionto the border of one or more pixels surrounding the overlay.Alternatively, the image data of the photo captured by the user maycorrespond to entire image rendered by the camera of the mobile devicein the viewport. In some embodiments, the mobile device may captureimage data corresponding to an entire area of the display of the mobiledevice. The mobile device may discard the image data outside of thesemi-translucent overlay corresponding to the micro area of the vehicledamaged in the accident. The discarded image data may correspond to themacro area of the vehicle not included in the micro area. Thenon-discarded image data may be stored such that the stored image datais smaller in size than the captured image data. After the photo hasbeen taken, mobile device 120 may transmit the data corresponding to thephoto to pre-FNOL system 140 for processing. Such processing may besimilar to the processing described above in regards to FIG. 8.

In some embodiments, the screen 506 may further include anaccordion-type, selectable field 506E wherein a user can reportmechanical issues with the vehicle. After selection, the accordion-type506E may expand and present the user with a plurality of sub-options tospecify the type and/or location of mechanical issues being experienced(e.g., vehicle won't start, engine making uncommon noises and/orrattling, etc.).

After receiving the detailed damage information and the pictures of thedamages, pre-FNOL system 140 may proceed to step 304 and provide theuser with contact information screen 508 as shown in FIG. 5C. Thecontact information screen 508 may include fields 508A, 508B, and 508Cwherein a user can provide contact information such as an email addressand a phone number. In some instances, the user may be required toconfirm the email address and phone number by providing a second entrymatching that of the first entry.

In the event of a non-anonymous pre-FNOL loss assessment in which theuser has previously provided login credentials associated with aninsurance account, the user may not be presented with screen 508 and notrequired to provide the required contact information denoted by fields508A, 508B, and 508C. However, in some instances, the user may berequired to provide the contact information stipulated by screen 508regardless of whether or not a non-anonymous pre-FNOL loss assessment isbeing conducted.

In the event of an anonymous pre-FNOL loss assessment, the user may bepresented with screen 508 and required to provide the required contactinformation denoted by fields 508A, 508B, and 508C. Additionally, thepre-FNOL system 140 may present the user with the unique control numbergenerated at step 210 associated with the anonymous pre-FNOL lossassessment that identifies the user. In such instances, screen 508 maycomprise information further detailing the unique control. Suchinformation may include an indication that the unique control number canbe entered to re-access data previously entered during the pre-FNOL lossassessment after submission and, further, that the unique control numbercan be used to convert a previously submitted pre-FNOL loss assessmentin to a claim or initiate services in instances in which a traditionalclaim is not filed.

In some instances, contact information screen 508 may additionallyinclude a payment preference field in which a user can specify a methodfor receiving payment at the conclusion of the pre-FNOL loss assessmentprocedures and subsequent claim filing. The payment account may be abanking and/or checking account, PayPal® account, Bitcoin account, orthe like. Payment, responsive to filing a claim, may come in the form ofdirect deposit or, in some instances, check. However, in the event of anon-anonymous pre-FNOL loss assessment, such information regardingpayment account preference may be previously provided by a user andstored in pre-FNOL system 140.

Alternatively, in the event of an anonymous pre-FNOL loss assessment, insome instances, contact information screen 508 may only present the userwith the unique contact control number and further information about theunique control number. As such, information screen 508 may not containthe contact information fields 508A, 508B, and 508C.

After receiving the contact information, pre-FNOL system 140 may proceedto step 306 and analyze the vehicle operation data received in step 202,the responses to the preliminary questions received in step 204, and thedetailed damage descriptions and photos received in step 302 in order todetermine repair costs for the damages to the vehicle and insurancepolicy effects associated with filing an insurance claim to cover thedetermined repair costs. In some instances, the loss assessment analysismay be performed by loss assessment server 160 in conjunction withhistorical data source server 150 and repair clearinghouse server 170.

For example, upon receiving the vehicle operation data, the responses tothe preliminary questions, the user vehicle selection information, andthe detailed damage descriptions and photos of the areas of the vehicledamaged in the accident, loss assessment server 160 may generate a lossassessment profile associated with the user who submitted theinformation. The loss assessment profile may include a loss assessmentmatrix comprising the data associated with the accident (e.g., vehicleoperation data, responses to the preliminary questions, vehicleselection information, and the detailed damages descriptions) and anaccident photo gallery including the photos of the areas of the vehicledamaged in the accident.

The loss assessment matrix may be a standardized m-by-n matrix storingthe data associated with the accident in numerical form. The data may beentered by the loss assessment server 160 in the order in which thecategory corresponding to the data is received from mobile device 120(e.g., vehicle operational data first, responses to the preliminaryquestions second, user vehicle selection information third, and thedetailed damage descriptions fourth). The order in which the datacategories are received may further correspond to the row or column ofthe loss assessment matrix into which the data is entered and stored. Inother words, the first category of data received (e.g., vehicleoperational data) may occupy the first row or first column of the lossassessment matrix. From there, loss assessment server 160 may enter eachindividual data item within the first category along the first row orthe first column in sequential matrix elements comprised within thefirst row or the first column. For example, in regards to the receivedvehicle operational data (e.g., the first category), the first elementwithin the first row or first column may be vehicle velocity at the timeof the accident, the second element within the first row or first columnmay be vehicle acceleration at the time of the accident, the thirdelement within the first row or first column may be the degree of brakeactivation during the time of the accident, and so on until each of thereceived data elements within the first category are entered into thefirst row or first column. After entering each of the received dataelements associated with the first category, the loss assessment matrixmay enter each of the received data elements within the second, third,and fourth categories in a manner similar to that described above withrespect to the first category.

In some instances, the loss assessment matrix may further include afifth category occupying a fifth row and/or column. The fifth categorymay be reserved for the type of damage to the vehicle, costs ofrepairing damages to the vehicle, type of repairs needed to fix thedamages to the vehicle, repair completion time, and accompanyinginsurance policy changes associated with filing a claim to cover thecalculated costs of repairing damages to the vehicle. As will bedescribed in further detail below, the loss assessment matrix may alsoinclude a sixth category occupying a sixth row and/or column. The sixthcategory may correspond to instances in which the user is provided withgeneral damage screen 606.

The entry of each data element within the rows or columns of the matrixmay be done in accordance with predetermined loss assessment matrixgeneration guidelines. As such, each of the loss assessment matricesgenerated by the loss assessment server 160 may be of a standardizedformat wherein each column and row position corresponds to a specificdata element. For example, the first data element of the first row andthe first column may correspond to the velocity of the vehicle at thetime of the accident in each loss assessment matrix generated by lossassessment server 160. Similarly, as will be discussed in further detailbelow, each of the loss assessment matrices stored in historical datasource database 154 may be of the same standardized format as that ofthe loss assessment matrices generated by loss assessment server 160wherein each column and row position corresponds to a specific dataelement.

In some instances, the data elements within a specific category may begreater or less than the data elements of other categories. For example,the first category (e.g., vehicle operational data) may include 25 dataelements, the second category (responses to preliminary questions) mayinclude 7 data elements, the third category (e.g., user vehicleselection information) may include 4 data elements, and the fourthcategory (e.g., detailed damage descriptions) may include 20 dataelements. In such instances, the category with the largest amount ofdata elements (e.g., the first category) may define the number ofcolumns in the loss assessment matrix or the number of rows in the lossassessment matrix depending on whether or not the data elements areentered in a row or column. Each of the remaining categories with fewerdata elements may include naught entries corresponding to the differencein data elements. For example, if the first category has 25 dataelements and the second category has 7 data elements, the secondcategory will include 18 naught entries.

Naught entries may also be provided for data expected to be received byloss assessment server 160, but not provided by telematics device 113,on-board computer 115 via vehicle communication systems 114, and/ormobile device 120.

The accident photo gallery may include photos provided by the userthrough mobile device 120 of the areas of the vehicle damaged in theaccident. Upon receipt of the photos, loss assessment server 160 mayinitially store the photos in one or more folders in the accident photogallery based on the areas of the vehicle damaged in the photos (e.g.,front, rear, driver side, and/or passenger side). Responsive to storingthe photos in the one or more folders, loss assessment server 160 maysort the photos of the damaged areas of the vehicle within the one ormore folders from a macro scale to micro scale in a manner similar tothat of the accordion-type, selectable fields discussed in regards toFIG. 5B and the sub-options included therein.

For example, in the event that the driver side portion of a vehicle wasdamaged in an accident and photos were provided to loss assessmentserver 160 capturing the damages to the driver side, the loss assessmentserver 160 may initially store each of the driver side damage photos inthe driver side folder of the accident photo gallery. Responsive tostoring the photos, loss assessment server 160 may arrange the photos inthe folder from the macro scale (e.g., the one or more photos of theentire driver side of the vehicle) to the micro scale (e.g., the one ormore photos of the specific damaged areas of the vehicle on the driverside).

In some instances, the micro scale photos may be arranged behind themacro scale photos according to the number of the option associated withthe reported damage. For instance, with respect to the example depictedin FIG. 5B, the photos taken corresponding to option 4 would be orderedahead of the photos taken corresponding to option 5, which would orderedahead of the photos taken corresponding to option 6. Through storing andstoring the photos in such a fashion, loss assessment server may be ableto increase processing speed associated with the calculation of thepre-FNOL loss assessment discussed below.

After loss assessment server 160 has generated the loss assessmentmatrix and the accident photo gallery of the loss assessment profile forthe accident associated with the user, loss assessment server 160 maytransmit the generated loss assessment matrix to the historical datasource server 150. The historical data source server 150 may compare theloss assessment matrix of the loss assessment profile against thetotality of historical loss assessment matrices of historical lossassessment profiles stored in historical data source database 154.

In determining a match and/or a hit of the loss assessment matrixagainst the totality of the historical loss assessment matrices storedin the historical data source database 154, the historical data sourceserver 150 may identify matches and/or hits based upon the correlationof one or more data elements shared by the matrices. Additionally, thehistorical data source server 150 may further associate a level ofconfidence to the overall quality of the match of the loss assessmentmatrix to each of the matched historical loss assessment matrices basedupon the total number of correlated data elements. For example, acorrelation of one data element will be given a minimum confidencelevel, whereas a correlation of each and every data element will begiven a maximum confidence level.

In some instances, each of the data elements of loss assessment matricesmay be weighted. The weight for each of the data elements may bedetermined based upon the impact the data element has in determining thecost of repairing damage to the vehicle and accompanying changes to theinsurance policy. For example, the data elements associated with themake and model of the vehicle may be weighted more heavily than the dataelement associated with the level of braking at the time of theaccident. The weights associated with each of the data elements maycontribute to the determination of the level of confidence to theoverall quality of the match of the loss assessment matrix to each ofthe matched historical loss assessment matrices based upon the totalnumber of correlated data elements. For example, a correlation of onedata element associated with a higher weight (e.g., vehicle model) willbe given a higher confidence level than a correlation of one dataelement associated with a lower weight (e.g., level of braking at thetime of the accident).

In other instances, each of the data elements of the loss assessmentmatrices may be associated with two weights. The first weight for eachof the data elements may be determined based upon the impact the dataelement has in determining the cost of repairing damage to the vehicle.The second weight for each of the data elements may be determined basedupon the impact the data element has in determining the accompanyingchanges to the insurance policy. The first weight and the second weightfor each data element may be independent of each other. For example, inregards to the data element corresponding to the model of a vehicle, thefirst weight associated with the cost of repairing damage to the vehiclemay be greater than the second weight associated with the accompanyingchanges to the insurance policy. Similarly, in regards to the dataelement corresponding to the velocity of the vehicle at the time ofaccident, the first weight associated with the cost of repairing damageto the vehicle may be less than the second weight associated with theaccompanying changes to the insurance policy.

In such instances in which a first and a second weight are associatedwith each data element of the loss assessment matrices, the historicaldata source server 150 may determine a first confidence rating for theoverall quality of the match of the loss assessment matrix to each ofthe historical loss assessment matrices based upon the total number ofcorrelated data elements in regards to the cost of repairing the vehicleand a second confidence rating in regards to the accompanying changes tothe insurance policy. For example, the loss assessment matrix may bematched against a historical loss assessment matrix based on acorrelation of one data element. The data element may be associated witha first weight and second weight, wherein the first weight is greaterthan the second weight. Accordingly, the first confidence rating inregards to the cost of repairing the vehicle may be greater than thesecond confidence rating in regards to the accompanying changes to theinsurance policy.

The weight(s) associated with each data element of the plurality of dataelements comprised within the loss assessment matrices and theconfidence level(s) and/or rating(s) associated with the quality of theoverall match of the loss assessment matrix to one or more historicalloss assessment matrices may be configured to dynamically change overtime. The changes may be determined by machine learning algorithms(e.g., Hidden Markov Model, Recurrent Neural Net, etc.) configured toplace additional emphasis on the most recent historical loss assessmentprofile data included in historical data source database 154.

In another example, the historical data source server 150 may perform apreliminary search of the loss assessment matrix against the historicalloss assessment matrices stored in the historical data source database154. Specifically, the historical data source server 150 may conduct asearch of the historical loss assessment matrices stored in thehistorical data source database 154 based on the vehicle make, model,and damage location indicated by the associated data elements within theloss assessment matrix. In the event that a plurality of hits and/ormatches are determined, historical data source server 150 may perform asecond search of the loss assessment matrix against the preliminarilymatched historical loss assessment matrices based on the remainder ofthe data elements of the loss assessment matrix. The second search maybe performed to determine the overall quality of the match of the lossassessment matrix to each of the matched historical loss assessmentmatrices in the manner described in any of the above-mentioned examples.

After the historical data source server 150 has compared the lossassessment matrix of the loss assessment profile against the totality ofhistorical loss assessment matrices of historical loss assessmentprofiles stored in historical data source database 154 and hasdetermined one or more matches and/or hits, historical data sourceserver 150 may transmit the historical loss assessment profilescorresponding to the historical loss assessment matrices of the one ormore matches and/or hits stored in historical data source database 154to loss assessment server 160.

In some instances, historical data source server 150 may only transmithistorical loss assessment profiles stored in historical data sourcedatabase 154 including historical loss assessment matrices that arematched against the loss assessment matrix with a specific level ofconfidence (e.g., 50% confidence, 90% confidence, greater than or equalto 70% confidence, greater than 85% confidence, etc.). In otherinstances, historical data source server 150 may only transmithistorical loss assessment profiles including historical loss assessmentmatrices comprising a certain amount of matched data elements (e.g., 10matched data elements, 35 matched data elements, etc.). Alternatively,historical data source server 150 may transmit all historical lossassessment profiles to loss assessment server 160, historical lossassessment profiles with historical loss assessment matrices includingdata elements corresponding to the make and model comprised within theloss assessment matrix, or historical loss assessment profiles withhistorical loss assessment matrices including data elementscorresponding to the make, model, and damage location (e.g., front,rear, passenger side, driver side) corresponding to the make, model, anddamaged location comprised within the loss assessment matrix.

In one example, historical data source server 150 may transmit a firstgroup of historical loss assessment profiles and a second group ofhistorical loss assessment profiles. The first group of historical lossassessment profiles sent by historical data source server 150 to lossassessment server 160 may be associated with the first confidence ratingfor the overall quality of the match of the loss assessment matrix toeach of the historical loss assessment matrices based upon the totalnumber of correlated data elements in regards to the cost of repairingthe vehicle. The second group of historical loss assessment profilessent by historical data source server 150 to loss assessment server 160may be associated with the second confidence rating for the overallquality of the match of the loss assessment matrix to each of thehistorical loss assessment matrices based upon the total number ofcorrelated data elements in regards to the accompanying changes to theinsurance policy. Historical data source server 150 may only transmithistorical loss assessment profiles of the first group and the secondgroup that are matched against the loss assessment matrix with aspecific confidence rating (e.g., 50% confidence, 90% confidence,greater than or equal to 70% confidence, greater than 85% confidence,etc.). In other instances, historical data source server 150 may onlytransmit historical loss assessment profiles of the first and secondgroups including historical loss assessment matrices comprising acertain amount of matched data elements (e.g., 10 matched data elements,35 matched data elements, etc.). Alternatively, historical data sourceserver 150 may transmit all historical loss assessment profiles of thefirst and second groups to loss assessment server 160, historical lossassessment profiles of the first and second groups with historical lossassessment matrices including data elements corresponding to the makeand model comprised within the loss assessment matrix, or historicalloss assessment profiles of the first and second groups with historicalloss assessment matrices including data elements corresponding to themake, model, and damage location (e.g., front, rear, passenger side,driver side) corresponding to the make, model, and damaged locationcomprised within the loss assessment matrix.

Upon receiving the historical loss assessment profiles from historicaldata source server 150, loss assessment server 160 may compare the oneor more vehicle damage pictures stored in the accident photo gallery tothe one or more historical vehicle damage pictures included in thehistorical accident photo galleries of the historical loss assessmentprofiles received from historical data source server 150. The comparisonmay be done through image recognition analysis, pattern recognitionanalysis, and/or object recognition analysis.

During the comparison, loss assessment server 160 may sequentiallycompare the vehicle damage pictures stored in the accident photo galleryto each of the historical vehicle damage photos stored in the historicalaccident photo galleries. The comparison performed by loss assessmentserver 160 may commence with a comparison of the historical accidentphoto gallery associated with the historical loss assessment matrixmatched with the highest level of confidence by historical data sourceserver 150. In instances in which first and second confidence levelswere determined, loss assessment server may base commencement off of thefirst confidence level (e.g., confidence level associated withcalculating the cost of repairing the vehicle). Loss assessment server160 may perform the comparison by first comparing the macro damagepictures of the front, rear, driver side, and/or passenger side of theuser's vehicle to the one or more historical macro damage picturesassociated with the corresponding vehicle areas and then comparing themicro damage pictures of the of the specific damage areas of the vehiclewithin the front, rear, driver side, and/or passenger side to thecorresponding vehicle areas with the one or more historical micro damagepictures.

The damage comparison of the macro and micro damage pictures performedthrough image recognition analysis, pattern recognition analysis, and/orobject recognition analysis may generate a match rating corresponding tothe overall similarities between the compared macro and micro pictures.Based on the match rating, loss assessment server 160 may determinewhether or not an additional damage comparison needs to be performed forthe historical accident photo gallery associated with the historicalloss assessment matrix matched with the next highest level ofconfidence. For example, if the match rating exceeds a certain scorethreshold, loss assessment server 160 may be able to determine that thematch is of a quality necessary to provide the user with a high accuracyrepair cost estimation (e.g., fixed bid estimate). Conversely, if thematch rating does not exceed a certain score threshold, loss assessmentserver 160 may be able to determine that analysis of the otherhistorical accident photo galleries provided by historical data sourceserver 150 is necessary. In response to such a determination, lossassessment server 160 may proceed to analyze the historical accidentphoto gallery associated with the historical loss assessment matrixmatched with the next highest level of confidence. The loss assessmentserver 160 may sequentially analyze the historical accident photogalleries in the above-mentioned fashion until a match rating is yieldedexceeding the threshold necessary to provide the user with ahigh-accuracy repair cost estimation.

In some instances, the loss assessment server 160 may perform a firstdamage comparison to consolidate the historical vehicle damage picturesprovided by the historical data source server 150 and a second damagecomparison to determine match ratings for the specific historicalvehicle damage pictures from the consolidated historical vehicle damagepictures produced by the first damage comparison.

During the first damage comparison, loss assessment server 160 maycompare the one or more macro damage pictures of the front, rear, driverside, and/or passenger side of the user's vehicle provided in step 302to the one or more historical macro damage pictures associated with thecorresponding vehicle areas. For example, in the event that the driverside portion of the user's vehicle was damaged in an accident and macropictures were provided to loss assessment server 160 of the damages tothe driver side of the user's vehicle, the first damage comparisonperformed by loss assessment server 160 may compare each of the macrovehicle driver side damage pictures to each of the historical macrovehicle driver side damage pictures. The loss assessment server 160 mayconsolidate the number of historical accident photo galleries based onhits and/or matches yielded during the first damage comparison by onlyadding hit and/or matched historical accident photo galleries to thecomparison pool for the second damage comparison.

In some instances, the hits and/or matches yielded during the firstdamage comparison may be determined based on a correlation of thespecific location of damage within the larger area of the vehicle. Forexample, in the event that the driver side front door of the user'svehicle was damaged in the accident and the macro pictures provided tothe loss assessment server 160 captured such damage, hits and/or matcheswould be determined for macro historical vehicle pictures alsoindicating damage to the driver side front door. Additionally, and/oralternatively, the hits and/or matches yielded during the first damagecomparison may be determined in a piecemeal manner. For example, in theevent that driver side front door and the driver side rear tire well ofthe vehicle were damaged in the accident, loss assessment server 160 maydetermine one or more matches and/or hits corresponding to the damage tothe driver side front door, one or more matches and/or hitscorresponding to the damage to the driver side rear tire well, and/orone or more matches and/or hits corresponding to the damage to both thedriver side front door and the driver side rear tire well of thevehicle.

Responsive to generating one or more hits and/or matches from the firstdamage comparison, the loss assessment server 160 may then perform asecond damage comparison in which the one or more micro damage picturesof specific areas of the front, rear, driver side, and/or passenger sideof the user's vehicle are compared to the one or more historical microdamage pictures associated with the corresponding specific vehicleareas. As stated above, the second damage comparison may be performedagainst a consolidated list generated by the first damage comparison inorder to determine match ratings for the micro pictures. For example, inthe event that the driver side front door panel of the user's vehiclewas damaged in an accident and micro pictures were provided to lossassessment server 160 of the damages to the driver side front doorpanel, the second comparison performed by loss assessment server 160 maycompare each of the micro vehicle driver side damage pictures to each ofthe historical micro vehicle driver side damage pictures from theconsolidated list.

The second damage comparison performed by loss assessment server 160 maygenerate match ratings corresponding to the overall similarities betweenthe compared micro pictures. The loss assessment server 160 may analyzeeach of the generated match ratings to determine which, if any, of thematch ratings exceeds a first match rating threshold required forgenerating a high-accuracy repair cost estimation (e.g., fixed bidestimate). In the event that multiple match ratings exceed the firstmatch rating threshold, loss assessment server 160 may order thehistorical loss assessment profiles associated with the match ratingsbased on the level of confidence that the historical loss assessmentmatrix corresponding to historical loss assessment profile comprisingthe historical accident photo gallery was given by historical datasource server 150 in the loss assessment matrix analysis describedabove. In instances in which first and second confidence levels weredetermined by the historical data source server 150, loss assessmentserver 160 may order the historical loss assessment profiles based offof the first confidence level (e.g., confidence level associated withcalculating the cost of repairing the vehicle).

In the event that none of the match ratings exceed the first matchrating threshold, loss assessment server 160 may determine which, ifany, of the match ratings exceeds a second match rating threshold, lessthan the first match rating threshold, required for generating a lowaccuracy repair cost estimation (e.g., upper-bound estimate) as will bedescribed in further detail below. In instances in which multiple matchratings exceed the second match rating threshold, loss assessment server160 may order the historical loss assessment profiles associated withthe match ratings based on the level of confidence the historical lossassessment matrix corresponding to historical loss assessment profilecomprising the historical accident photo gallery was given by historicaldata source server 150 in the loss assessment matrix analysis. Ininstances in which first and second confidence levels were determined bythe historical data source server 150, loss assessment server 160 mayorder the historical loss assessment profiles based off of the firstconfidence.

If none of the match ratings exceed either the first or second matchrating thresholds, loss assessment server 160 may provide notificationto the user requesting pre-FNOL loss assessment that pre-FNOL lossassessment is unable to be determined and that traditional claimsprocessing is necessary. In such instances, loss assessment server 160may provide the user with a notification similar to that described atstep 208.

Responsive to performing the damage comparison of the macro and microdamage pictures and determining one or more matches and/or hits of themacro and micro pictures stored in the accident photo gallery againstthe historical micro and macro pictures stored in the historicalaccident photo gallery, loss assessment server 160 may provide the userwith a high-accuracy pre-FNOL loss assessment. In providing the userwith the high-accuracy pre-FNOL loss assessment, loss assessment server160 may extract repair data from the fifth category occupying the fifthrow and/or column of the historical loss assessment matrix correspondingto the matched and/or hit historical accident photo gallery.

For example, after generating a match rating for a historical accidentphoto gallery exceeding the threshold necessary to provide the user witha high-accuracy repair cost estimation, loss assessment server 160 mayextract data from the historical loss assessment matrix corresponding tothe historical accident photo gallery associated with the generatedmatch rating. The data extracted from the historical loss assessmentmatrix may be repair data stored in the fifth category occupying thefifth row and/or column of the historical loss assessment matrix.Specifically, loss assessment server 160 may extract repair datacorresponding to the type of damage to the vehicle (e.g., damage to thedriver side front door window of the vehicle, damage to the rear lefttaillight of the vehicle, etc.), calculated costs of repairing damagesto the vehicle (e.g., repair costs associated with fixing the damage tothe driver side front door window of the vehicle, repair costsassociated with fixing the damage to the rear left taillight of thevehicle, etc.), repair time needed to fix the damages to the vehicle(e.g., amount of time required to repair the driver side front doorwindow and the rear left taillight of the vehicle, etc.), and type ofrepairs needed to fix the damages to the vehicle (e.g., replacement ofpower window mechanism of the driver side front door window of thevehicle, replacement of rear left taillight of the vehicle, etc.).

In some instances, after extracting the above-mentioned repair data,loss assessment server 160 may further analyze the historical lossassessment matrix corresponding to the extracted data in order todetermine a year associated with the accident detailed by the historicalloss assessment profile comprising the historical loss assessmentmatrix. Responsive to determining the year associated with the accident,loss assessment server 160 may adjust the associated repair costs toaccount for inflation.

Additionally and/or alternatively, loss assessment server 160 mayperform a part availability and cost analysis in relation to the type ofrepairs needed to fix the vehicle. Such an analysis may be performedwith respect to vehicles in excess of 10 years old. For example, in theevent that the user's vehicle is a 1995 Volvo 850 which sustained damageto the rear bumper during an accident requiring replacement of thebumper, loss assessment server may perform an analysis of theavailability of 1995 Volvo 850 rear bumpers and the costs associatedtherein. Responsive to performing such an analysis, in some instances,loss assessment server 160 may determine that the part required torepair the damage to the vehicle is unavailable. In such instances, lossassessment server 160 may perform a further analysis to determinewhether or not the unavailable part is interchangeable with a coincidingpart with a more contemporary vehicle of the same make. If thecoinciding part of a more contemporary vehicle is determined to beinterchangeable, loss assessment server 160 may determine a costassociated with the corresponding part as well as the labor costsassociated with installing the coinciding part. However, if thecoinciding part of a more contemporary vehicle is not determined to beinterchangeable, loss assessment server 160 may perform an additionalanalysis to determine if the vehicle should be written off.Alternatively, the loss assessment server 160 may provide notificationto the user requesting pre-FNOL loss assessment that pre-FNOL lossassessment is unable to be determined and that traditional claimsprocessing is necessary. In such instances, loss assessment server 160may provide the user with a notification similar to that described atstep 208.

After extracting the repair data from the historical loss assessmentmatrix, loss assessment server 160 may incorporate the extracted repairdata into the fifth category occupying the fifth row and/or column ofthe loss assessment matrix corresponding to the loss assessment profileassociated with the user. The incorporated repair data may comprise theadjusted repair costs to account for inflation, the applicability ofusing an interchangeable part and the costs associated therein, and thecosts associated with installing the interchangeable part.

Upon incorporating the extracted repair data from the historical lossassessment matrix into the loss assessment matrix corresponding to theloss assessment profile of the user, loss assessment server 160 may thendetermine the accompanying insurance changes associated with filing aclaim to cover the vehicle repair costs. In one example, loss assessmentserver 160 may determine the accompanying insurance changes based on theinsurance change data stored in the historical loss assessment matrixassociated with the historical accident photo gallery from which therepair costs were determined. In such an example, the loss assessmentserver 160 determine an insurance premium percentage increase for thehistorical loss assessment profile and apply a similar insurance premiumpercentage increase to an insurance premium corresponding to the lossassessment profile of the user.

In another example, the loss assessment server 160 may determine theaccompanying insurance changes associated with filing a claim to coverthe vehicle repair costs based upon an analysis of the historical lossassessment profiles sent by historical data source server 150 includedwithin the second group associated with the second confidence ratingcorresponding to the accompanying changes to the insurance policy.During the analysis, loss assessment server 160 may calculate aninsurance premium percentage increase for the historical loss assessmentprofile of the second group associated with the highest secondconfidence rating. The loss assessment server 160 may then apply asimilar insurance premium percentage increase to an insurance premiumcorresponding to the loss assessment profile of the user.

In either scenario, after determining the accompanying insurance policychanges associated with filing a claim to cover the vehicle repaircosts, loss assessment server 160 may incorporate the determinedaccompanying insurance policy changes into the fifth category occupyingthe fifth row and/or column of the loss assessment matrix correspondingto the loss assessment profile associated with the user.

Upon determining the repair costs and accompanying insurance policychanges, loss assessment server 160 may provide the determined repaircosts and the accompanying insurance policy changes to the user. Lossassessment server 160 may transmit the determined repair costs and theaccompanying insurance policy changes to the user via email and/or textmessage to the email address and/or the phone number provided by theuser at step 304 through contact information screen 508. Additionallyand/or alternatively, loss assessment server 160 may be configured totransmit the determined repair costs and the accompanying insurancepolicy changes to the user via a pre-FNOL loss assessment applicationoperating on mobile device 120 of the user and/or a pre-FNOL lossassessment web application being accessed by an internet browserapplication operating on mobile device 120.

In instances in which loss assessment server 160 transmits thedetermined repair costs and the accompanying insurance policy changes tothe user via a pre-FNOL loss assessment application and/or a pre-FNOLloss assessment web application, the user may be presented with lossassessment completion screen 510 shown in FIG. 5C. The loss assessmentcompletion screen 510 may include repair cost field 510A, repair timefield 510B, premium impact field 510C, “Save for Later” button 510D, and“File a Claim” button 510E.

The repair cost field 510A may include the determined repair cost of thevehicle, the user's deducible, and the claim payment amount (e.g., thenumerical difference between the cost of repair and the deductible) if aclaim were to be filed. In regards to the determined repair cost of thevehicle, there may be an option for the user to “View Details” regardingthe determined repair costs. After user selection of the “View Details”option, loss assessment server 160 may provide the user with an itemizedbreakdown of the damages and the costs related thereto including thetype of damage to the vehicle, calculated costs of repairing damages tothe vehicle, and type of repairs needed to fix the damages to thevehicle.

In regards to the user's deductible, depending on whether or not theuser previously provided login information associated with an insurancepolicy account of the user, the deductible may be a filled entry asshown in loss assessment completion screen 510 or the deductible may bea fillable entry (not shown). For example, in the event that the userhas not previously provided insurance account login information topre-FNOL system 140, the user may be able and/or required to type intheir deducible into the deductible area of repair cost field 510A.Alternatively, in instances in which the user has previously providedinsurance account login information to pre-FNOL system 140, the lossassessment server 160 may embed the deductible associated with theuser's insurance account into the repair cost field 510A. Additionally,there may be a selectable “View Policy” option that the user may be ableto select in order to receive detailed information regarding the user'sinsurance policy. After user selection of the “View Policy” option, lossassessment server 160 may provide the user with detailed informationabout the user's insurance policy. In some instances, loss assessmentserver 160 may also provide the contact information of the user'sinsurance agent so that the user may discuss their insurance plan withthe agent.

In instances in which the user has not previously provided insuranceaccount login information to pre-FNOL system 140, the loss assessmentserver 160 may prompt the user to provide insurance account logininformation and/or to enter their deductible before calculating theclaim payment amount. As will be discussed in further detail below, theuser may be required to provide login information associated with theirinsurance account in order to be able to file a claim to cover thedetermined repairs costs.

The repair time field 510B may include an estimated repair completiontime associated with the time estimated for repairing the damage to theuser's vehicle and a user-selectable “Find a Repair Shop” option. Theestimated repair completion time may be determined by loss assessmentserver 160 by extracting the completed repair time from the historicalloss assessment matrix used in determining the repair costs for thevehicle. In some instances, as will be discussed below, the estimatedrepair completion time may be dependent on the user's selection of arepair shop under the “Find a Repair Shop” option.

The “Find a Repair Shop” option may be a user-selectable option that,when selected, causes loss assessment server 160 to transmit the user'sloss assessment profile to repair clearinghouse server 170. Upon receiptof the user's loss assessment profile, repair clearinghouse server 170may extract geographical location information corresponding to the userand may generate a map through the pre-FNOL loss assessment applicationoperating on mobile device 120 of the user and/or a pre-FNOL lossassessment web application being accessed by an internet browserapplication operating on mobile device 120. The geographical locationassociated with the mobile device 120 of the user may be used by repairclearinghouse server 170 to localize the map corresponding to the user'sgeographical location. Additionally, repair clearinghouse server 170 mayrender one or more pins on the map corresponding to repair shops in theuser's immediate area based on the user's geographical location. Each ofthe pins associated with a particular repair shop may be auser-selectable pin. Once selected, repair clearinghouse server 170 maygenerate a repair shop specific screen on the pre-FNOL loss assessmentapplication and/or the pre-FNOL loss assessment web application. Therepair shop specific screen may provide data about the repair shop suchas an address, telephone number, pictures of the repair shop, picturesof repair shop employees, types of services performed by the repairshop, and the like. Furthermore, the repair shop specific screen maydisplay a rating and comment section wherein patrons of the repair shopmay provide feedback and a repair shop availability schedule. Throughthe repair shop availability schedule, a user may be able to see therepair shop's availability, forecast a repair completion time for thetype of repairs needed, and schedule a repair with the repair shop.

In regards to forecasting a repair completion time, repair clearinghouseserver 170 may associate the repair cost with one of three colorscorresponding to an estimated time range needed to perform repairs basedon the determined repair cost. For example, if the repair cost of thevehicle is less than or equal to $3,000, repair clearinghouse server 170may associate the repair cost with the color green, if the repair costis greater than $3,000 but less than or equal to $6,000, repairclearinghouse server 170 may associate the repair cost with the coloryellow, and if the repair cost is greater than $6,000, repairclearinghouse server 170 may associate the repair cost with the colorred. Each of the repair colors (e.g., green, yellow, and red) may beassociated with a time of repair completion range. For instance, greenrepairs may be associated with a range of one to ten days, yellowrepairs may be associated with a range of ten to 25 days, and redrepairs may be associated with a range of 25 to 50 days.

Additionally, each of the repair shops may list availability based onthe repair colors (e.g., green, yellow, and red). For example, a repairshop proximate to the user's geographical location may have ten slotsper month available for green repairs, seven slots per month availablefor yellow repairs, and two slots per month available for red repairs.The forecasted repair completion time for each of the respective repaircolors may vary within the approximate ranges based on the number ofvehicles associated with the specific color currently undergoing repairand/or scheduled to be repaired. For example, if a vehicle determined asa green repair schedules a repair at a repair shop with no green repairsunderway and/or scheduled, the forecasted repair completion time may beone day. Conversely, if a vehicle determined as a green repair schedulesa repair at a repair shop with no green repairs underway but six greenrepairs scheduled ahead of the vehicle, the forecasted repair completiontime may be six days. Thus, responsive to scheduling a repair with arepair shop, the repair time field 510B of screen 510 may indicate arepair completion time specific to the repair shop.

In some instances, the “Find a Repair Shop” option may be auser-selectable option that, when selected, causes repair clearinghouseserver 170 to generate a sortable list through the pre-FNOL lossassessment application operating on mobile device 120 of the user and/ora pre-FNOL loss assessment web application being accessed by an internetbrowser application operating on mobile device 120. The sortable listmay display each of the repair shops within the geographical locationassociated with the mobile device 120 of the user, starting with thenearest repair shop to the geographical location associated with themobile device 120 and terminating with the repair shop furthest from thegeographical location associated with the mobile device 120. The user ofmobile device 120 may be able to sort the repair shop data comprisedwithin the sortable list based on factors such as highest repairranking, nearest location, repair color availability, and the like. Insome instances, the user may be able to toggle between the map interfaceand the sortable list interface.

The premium impact field 510C may include insurance policy updateinformation that a user may expect responsive to filing a claim to coverthe determined repair costs. In particular, the premium impact field510C may include the six month total premium cost and the expected rateincrease of the insurance premium. The calculation of the six monthtotal premium cost and the expected rate increase of the insurancepremium may depend on whether or not the user previously provided logininformation associated with an insurance policy account of the user. Forexample, in the event that the user has not previously providedinsurance account login information to pre-FNOL system 140, the user maybe able and/or required to provide login information associated with aninsurance account covering the damaged vehicle in order to receive thepremium increase calculations. Alternatively, the user may be able toenter their current six month premium cost information into field 510Cand loss assessment server 160 may be able to calculate the six monthpremium changes based on the user entered six month premium costinformation.

Additionally, in the premium impact field 510C, there may be aselectable “Learn More” option that the user may be able to select inorder to receive detailed information regarding the cost increases tothe user's insurance premium. After user selection of the “Learn More”option, loss assessment server 160 may provide the user with detailedinformation about the user's insurance policy and the cost increases tothe user's insurance premium. In some instances, loss assessment server160 may provide the contact information of the user's insurance agent sothat the user may discuss cost increases to the user's insurance premiumassociated with filing a claim.

At the bottom of loss assessment completion screen 510 there may be a“Save for Later” user-selectable button 510D and a “File a Claim”user-selectable button 510E. Responsive to a user selection of the “Savefor Later” button 510D, loss assessment server 160 store the informationshown in fields 510A, 510B, and 510C for later review by the user.Additionally, loss assessment server 160 may indicate a time period inwhich the captured repair cost information and accompanying insurancepolicy change information will be held. The loss assessment server 160may further indicate to the user that after expiration of the timeperiod, the captured repair cost information and accompanying insurancepolicy change information may change.

At step 308, responsive to a user selection of the “File a Claim” button510E, loss assessment server 160 may determine whether or not the userhas previously logged into an insurance account associated with thedamaged vehicle. In the event that the user has previously logged intothe insurance account, loss assessment server 160 may provide claimpayment equivalent to the claim payment amount shown in field 510A(e.g., the difference between the user's deductible and the determinedrepair costs). The claim payment may be provided to the user in themanner specified by the user through the payment preference field (e.g.,through direct deposit to a banking and/or checking account, PayPal®account, Bitcoin account, or the like). Depending on the user specifiedpreference, in some instances, the loss assessment server 160 mayfacilitate payment in the form of a check.

In some instances, after the user has selected the “File a Claim” button510E and payment has been provided to the user by loss assessment server160, repair clearinghouse server 170 may provide the user with thesortable list and/or map of repair shops proximate to the geographicallocation associated with the mobile device 120 of the user. Thepresentation of the sortable list and/or map of repair shops and thefunctionality related therein may be similar to that described above inregards to the user selection of the “Find a Repair Shop” option.Alternatively, in the event that the user previously selected a specificrepair shop at which to repair the damages to their vehicle, repairclearinghouse server 170 may not provide the user with the sortable listand/or map of repair shops.

Additionally, after the user has selected the “File a Claim” button 510Eand selected a repair shop, repair clearinghouse server 170 may extractthe user's response to field 502B of screen 502 in FIG. 5A regarding thedrivability of the user's vehicle. In the event that the user hasresponded that the user's vehicle is not driveable, repair clearinghouseserver 170 may provide the user with a sortable list and/or map of towtruck companies proximate to the geographical location associated withthe mobile device 120 of the user. The presentation of the sortable listand/or map of tow truck companies and the functionality related thereinmay be similar to that described above in regards to the user selectionof the “Find a Repair Shop” option. Furthermore, repair clearinghousesever 170 may also provide the user with a sortable list and/or map ofrental car agencies proximate to the user's geographical location. Insome instances, the repair clearinghouse server 170 may enable the userto populate the sortable list and/or map with both rental car agenciesand tow truck companies proximate to the user. The presentation of thesortable list and/or map of rental car agencies and the functionalityrelated therein may be similar to that described above in regards to theuser selection of the “Find a Repair Shop” option.

Alternatively, in the event that the user has selected a low accuracypre-FNOL loss assessment (e.g., less accurate anticipated repair costand/or upper bound repair cost) at step 216 of the pre-FNOL lossassessment method shown in FIG. 2, the pre-FNOL system 140 may proceedto step 402 of the low accuracy pre-FNOL loss assessment method shown inFIG. 4. In some instances, the user may not need to be logged in to anaccount of an associated insurance provider in order to receive a lowaccuracy pre-FNOL loss assessment. However, in other instances, the usermay need to be logged in to an account of an associated insuranceprovider in order to receive a low accuracy pre-FNOL loss assessment.

At step 402, the pre-FNOL system 140 may provide the general damagedescription screen 606, as shown in FIG. 6A, to the mobile device 120 ofthe driver of vehicle 110 regarding the accident. The general damagedescription screen 606 may include a damage level selection field 606Aand an estimated speed at time of impact field 606B.

The damage level selection field 606A may present the user with aplurality of historical vehicle damage photos. The historical vehicledamage photos presented to the user may be reproduced from one or moreof the historical accident photo galleries stored in the historical datasource database 154 of historical data source server 150. In the exampleshown in general damage description screen 606, pre-FNOL system 140 maypresent the user with three historical damage photos. Each of the threehistorical damage photos presented to the user may correspond to adifferent damage level. For example, the first historical damage picturemay correspond to a first damage level, the second historical damagepicture may correspond to a second damage level greater than the firstdamage level, and the third historical damage picture may correspond toa third damage level greater than the first and second damage levels.Additionally, each of the first, second, and third damage level picturesmay be accompanied with a short text segment providing furtherdescription of the particular damage level of which it accompanies. Insome instances, the historical damage pictures may be of a random makeand model, while in other instances, the historical damage pictures maybe of the make and model of the user's vehicle.

In another example, pre-FNOL damage system 140 may present the user witha plurality of rounds of historical vehicle damage pictures. The firstround of historical vehicle damage pictures may include three historicaldamage pictures associated with the three most common types of vehicleaccidents. For example, the first historical damage picture may be ofdamage to the rear portion of the vehicle, the second historical damagepicture may be of damage to the front portion of the vehicle, and thethird historical vehicle damage picture may be of damage to a side ofthe vehicle. Alternatively, the first round of historical vehicle damagepictures may include three historical damage pictures associated withthe three most commonly selected historical vehicle damage pictures. Assuch, the first round of pictures presented to the user may change overtime responsive to user input. In either instance, the damage levelselection field 606A may further include a user-selectable “Damage NotListed” button that, if selected by the user, causes pre-FNOL system 140to display three new historical vehicle damage pictures corresponding toeither the next three most common types of vehicle accidents or the nextthree most commonly selected vehicle damage pictures.

After the user selection of one or more of the displayed historicaldamage pictures in the first round, pre-FNOL system 140 may present theuser with a second round of historical vehicle damage pictures. Thethree historical vehicle damage pictures comprised within the secondround of historical vehicle damage pictures may be determined bypre-FNOL system 140 based on the user's one or more historical vehicledamage picture selections from the first round. For example, in theevent that the first round of historical damage pictures includedhistorical damage pictures associated with the three most common typesof vehicle accidents and the user selected a historical vehicle damagepicture depicting damage to the rear of a vehicle, pre-FNOL system 140may present the user with three historical damage pictures in the secondround corresponding to a variance of damage location within the rearlocation of the vehicle. For instance, the three historical damagepictures presented to the user in the second round may depict damage tothe bumper of a vehicle, back windshield of a vehicle, taillight of avehicle, and the like. In some instances, the three historical damagepictures presented to the user in the second round may correspond to thethree most commonly damaged areas of the vehicle corresponding to thetype of accident in which the vehicle was involved. Furthermore, thedamage level selection field 606A may still include the user-selectable“Damage Not Listed” button that, if selected by the user, causespre-FNOL system 140 to display three new historical vehicle damagepictures corresponding to either three new areas of vehicle damagewithin the larger area of the vehicle or the next three most commonlydamaged areas of the vehicle within the larger vehicle area.

Similarly, in the event that the first round of historical damagepictures included the three most commonly selected historical damagepictures, pre-FNOL system 140 may present the user with three historicaldamage pictures in the second round that are most commonly selected byusers in relation to their selection of one or more pictures in thefirst round. For example, in the event that the user selected ahistorical damage picture depicting damage to the front of a vehicle inthe first round, pre-FNOL system 140 may present the user with threehistorical damage pictures in the second round of the most commonlyselected historical vehicle damage pictures corresponding to the frontof the vehicle. For instance, the historical damage pictures presentedto the user in the second round may correspond to damage areas withinthe front portion of the vehicle most commonly selected by users (e.g.,hood, front bumper, headlight, etc.). In some instances, a userselection of the user-selectable “Damage Not Listed” button may causepre-FNOL system 140 to display three new historical vehicle damagepictures corresponding to the next three most commonly selectedhistorical vehicle damage pictures in relation to the one or morehistorical vehicle damage pictures selected by the user in the firstround.

In some instances, the rounds may be further associated with ahistorical vehicle damage theme. For example, the first round ofhistorical vehicle damage photos may be concerned with ascertainment ofa macro damage location (e.g., front of vehicle, rear of vehicle, driverside of vehicle, passenger side of vehicle). The second round ofhistorical vehicle damage pictures may be concerned with theascertainment of a micro damage location within the greater macro damagelocation determined in the first round. A third round of historicaldamage pictures may be concerned with the ascertainment of a level ofdamage to the micro area of the greater macro area determined in thefirst and second rounds. In some instances, the historical vehicledamage themes may be presented in multiple rounds depending on userselections of the historical vehicle damage pictures. For example, thedetermination of the macro damage location may occur across the firstand second rounds, the determination of the micro damage location withinthe macro damage location may occur across the third and fourth rounds,and the determination of the level of damage to the micro locationwithin the macro location may occur in the fifth and sixth rounds.

Pre-FONL system 140 may provide the user with rounds of historicaldamage pictures until a certain level of confidence is reached based theuser selections required to provide the user with a low accuracypre-FNOL loss assessment. As such, the user may be provided with aplurality of rounds of historical damage pictures (e.g., one round, tworounds, five rounds, etc.) wherein each round is associated with aparticular amount of confidence points (e.g., 1 point, 3 points, etc.).The amount of points awarded per round may increase, decrease, or remainconstants. Additionally and/or alternatively, each of the historicaldamage pictures included with each round may be associated withdifferent confidence point amounts. For example, a first historicaldamage picture in the first round may be associated with 1 confidencepoint, a second historical damage picture in the first round may beassociated with 3 confidence points, and the third historical damagepicture in the first round may by associated with 2 confidence points.The pre-FNOL system 140 may provide the user with rounds of historicaldamage photos until a particular confidence level (e.g., particularconfidence point tally) is reached. The confidence point tally may be 10points, 15 points, 30 points, etc.

Once the user has surpassed the necessary point tally required toperform the low accuracy loss assessment, pre-FNOL system 140 may ceaseto provide the user with additional rounds of historical damagepictures. However, in some instances, pre-FNOL system 140 may provide amessage to the user upon reaching the necessary point tally associatedwith performing the low accuracy pre-FNOL loss assessment inquiringwhether or not the user would like to provide responses to additionalrounds of historical damage pictures in order to be able to receive ahigh accuracy loss assessment. Upon receiving a user response in theaffirmative, pre-FNOL system 140 may provide additional rounds ofhistorical loss assessment pictures until a confidence point tally isreached associated with performing a high accuracy loss assessment. Theconfidence point tally associated with performing the high accuracy lossassessment may be 20 points, 30 points, 60 points, etc.

Regardless of whether the user performs a low accuracy pre-FNOL lossassessment or a high accuracy pre-FNOL via the general damagedescription screen 606, pre-FNOL system 140, in some instances, mayrequire a user to provide one or more photos of areas of their vehicledamaged in accident responsive to the user surpassing the confidencepoint tally associated with the either the low or high accuracyassessment. The one or more accident pictures provided by the user maybe utilized by pre-FNOL system 140 to determine if the user has selectedhistorical damage pictures corresponding to the damages of theirvehicle.

Furthermore, general damage description screen 606 may include estimatedspeed at time of impact field 606B. The estimated speed at time ofimpact field 606B may be a dropdown field which, when selected, providesthe user with a plurality of velocity values from which to choose (e.g.,0 mph, 20 mph, 60 mph, etc.). In some instances, the user may beprompted with the estimated speed at time of impact field 606B prior tothe historical damage pictures are provided to the user. Thus, pre-FNOLsystem 140 may be able to provide the user with historical vehicledamage pictures associated with the velocity of the user's vehicle atthe time of the accident and, as such, provide the user with moreaccurate historical damage pictures.

In some instances, general damage description screen 606 may include aplurality of additional dropdown fields similar to that of estimatedspeed at time of impact field 606B. Such dropdown fields may include amacro vehicle damage location field (e.g., front, rear, driver side,passenger side), a type of vehicle accident field (frontal collision,rear end collision, T-bone collision, etc.), and the like. Based uponthe user's selections to the questions put forth by the additionaldropdown fields, pre-FNOL system 140 may be able to provide the userwith historical damage pictures more efficiently and accurately.

Alternatively, in instances in which pre-FNOL system 140 receivedvehicle operational data at step 202 including data corresponding to thevehicle velocity at the time of the accident, pre-FNOL system 140 maynot include estimated speed at time of impact field 606B in generaldamage description screen 606. Instead, pre-FNOL system 140 may onlyinclude the plurality of additional dropdown fields described above(e.g., macro vehicle damage field, type of vehicle accident field, andthe like).

In any event, after receiving the general damage information, pre-FNOLsystem 140 may proceed to step 404 and provide the user with contactinformation screen 608 as shown in FIG. 6B. The contact informationscreen 608 may be similar to that of contact information screen 508 asdescribed in detail above. Accordingly, contact information screen 608may include fields 608A, 608B, and 608C wherein a user can providecontact information such as an email address and a phone number. In someinstances, the user may be required to confirm the email address andphone number by providing a second entry matching that of the firstentry.

In the event of a non-anonymous pre-FNOL loss assessment in which theuser has previously provided login credentials associated with aninsurance account, the user may not be presented with screen 608 and notrequired to provide the required contact information denoted by fields608A, 608B, and 608C. However, in some instances, the user may berequired to provide the contact information stipulated by screen 608regardless of whether or not a non-anonymous pre-FNOL loss assessment isbeing conducted. In the event of an anonymous pre-FNOL loss assessment,the user may be presented with screen 608 and required to provide therequired contact information denoted by fields 608A, 608B, and 608C.

In some instances, contact information screen 608 may additionallyinclude a payment preference field in which a user can specify a methodfor receiving payment at the conclusion of the pre-FNOL loss assessmentprocedures and subsequent claim filing. The payment account may be abanking and/or checking account, PayPal® account, Bitcoin account, orthe like. Payment, responsive to filing a claim, may come in the form ofdirect deposit or, in some instances, check. However, in the event of anon-anonymous pre-FNOL loss assessment, such information regardingpayment account preference may be previously provided by a user andstored in pre-FNOL system 140.

After receiving the contact information, pre-FNOL system 140 may proceedto step 406 and analyze the vehicle operation data received in step 202,the responses to the preliminary questions received in step 204, thevehicle selection data received in step 212 (or the vehicle profile datareceived in step 214), and the general damage descriptions received instep 402 in order to determine repair costs for the damages to thevehicle and insurance policy effects associated with filing an insuranceclaim to cover the determined repair costs. In some instances, the lossassessment analysis may be performed by loss assessment server 160 inconjunction with historical data source server 150 and repairclearinghouse server 170.

For example, upon receiving the vehicle operational data, the responsesto the preliminary questions, the user vehicle selection information (orthe vehicle profile information), and the general damage descriptions ofthe vehicle damaged in the accident, loss assessment server 160 maygenerate a loss assessment profile associated with the user whosubmitted the information. The loss assessment profile may include aloss assessment matrix comprising the data associated with the accident(e.g., vehicle operation data, responses to the preliminary questions,vehicle selection information, and the detailed damages descriptions)and an accident photo gallery including the photos of the areas of thevehicle damaged in the accident.

The loss assessment matrix produced by loss assessment server 160 may besimilar to the loss assessment matrices described above. However, inregards to the fourth category occupying the fourth row or column, whichcorresponds to the detailed damage description data, loss assessmentserver 160 may insert naught entries for each of the data elements.Instead, loss assessment server 160 may fill the sixth categoryoccupying the sixth row or column with data provided by the user viageneral damage description screen 606. Loss assessment server 160 mayenter each individual data item within the sixth category along thesixth row or the sixth column in sequential matrix elements comprisedwithin the sixth row or the sixth column. In the first element withinthe sixth row or column, loss assessment server 160 may enter datacorresponding to the estimated speed at time of impact field 606B. Inthe event that such data was previously received at step 202, lossassessment server 160 may enter a naught entry in the first element.Next, loss assessment server 160 may enter data corresponding to theadditional dropdown fields in sequential data elements. In instances inwhich such fields are not provided to the user in general damage screen606, loss assessment server 160 may enter naught entries for those dataelements. In regards damage level selection field 606A, loss assessmentserver may enter a numerical identifier associated with each chosenhistorical vehicle damage picture in sequential data elements.

After loss assessment server 160 has created the loss assessment matrix,loss assessment server may create an accident photo gallery for the lossassessment profile of the user. In the accident photo gallery, lossassessment server 160 may include the one or more vehicle damagepictures provided by the user after the confidence point tally foreither of the low accuracy pre-FNOL loss assessment or high accuracypre-FNOL loss assessment has been reached.

Upon generation of the loss assessment matrix and the accident photogallery of the loss assessment profile associated with the user, lossassessment server 160 may provide the loss assessment matrix tohistorical data source server 150. The historical data source server 150may compare the loss assessment matrix of the loss assessment profileagainst the totality of historical loss assessment matrices ofhistorical loss assessment profiles stored in historical data sourcedatabase 154.

Historical data source server 150 may perform a first comparison of theloss assessment matrix against the totality of the historical lossassessment matrices stored in the historical data source database 154 inregards to the repair costs associated with repairing damages to theuser's vehicle and a second comparison of the loss assessment matrixagainst the totality of the historical loss assessment matrices 154 inregards to the accompanying insurance policy changes associated withfiling a claim to cover the repair costs.

In the first comparison, historical data source server 150 may comparethe numerical identifiers corresponding to the first and last historicalvehicle damage picture selections of the user during the presentation ofhistorical vehicle damage pictures by damage level selection field 606A.In determining a match and/or a hit of the loss assessment matrixagainst the totality of the historical loss assessment matrices storedin the historical data source database 154 during the first comparison,the historical data source server 150 may identify matches and/or hitsbased on the correlation of the numerical identifier corresponding toeither the first and/or last user selected historical vehicle damagepicture. As such, historical data source server 150 may determine one ormore hits and/or matches corresponding to the first numericalidentifier, one or more hits and/or matches corresponding to the lastnumerical identifier and, in some instances, one or more hitscorresponding to the first and last numerical identifiers.

In the second comparison, historical data source server 150 may performa comparison of the loss assessment matrix against each of the pluralityof loss assessment matrices in the manner described above in regards tothe high accuracy pre-FNOL loss assessment. For example, historical datasource server 150 server may compare each data element comprised in theloss assessment matrix against each and data element comprised withineach of the historical loss assessment matrices. Each of the dataelements comprised within the loss assessment matrix may be associatedwith a weight corresponding to the effect the particular data elementhas in determining the insurance policy increases associated with filinga claim to cover the determined repair costs. The weight associated witheach of the data elements may contribute to the determination of thelevel of confidence to the overall quality of the match of the lossassessment matrix to each of the matched historical loss assessmentmatrices based upon the total number of correlated data elements. Forexample, a correlation of one data element associated with a higherweight will be given a higher confidence level than a correlation of onedata element associated with a lower weight.

Responsive to performing the first and second comparisons, historicaldata source server 150 may transmit the historical loss assessmentprofiles corresponding to the matches and/or hits determined during thefirst and second comparisons to loss assessment server 160 in order forthe repair costs and the accompanying insurance policy changes to bedetermined. Upon receiving the historical loss assessment profiles, lossassessment server 160 may extract the repair cost data from each of thehistorical loss assessment matrices comprising the numerical identifiercorresponding to the first user selected historical vehicle damagepicture and repair cost data from each of the historical loss assessmentmatrices comprising the numerical identifier corresponding to the lastuser selected historical vehicle damage picture. In determining therepair cost data, the loss assessment server 160 may take the average ofthe repair cost data extracted from each of the historical lossassessment matrices comprising the numerical identifier corresponding tothe first user selected historical vehicle damage picture. Additionally,loss assessment server 160 may take the average of the repair cost dataextracted from each of the historical loss assessment matricescomprising the numerical identifier corresponding to the last userselected historical vehicle damage picture. Responsive to producing theaveraged repair cost data corresponding to the first and last userselected historical vehicle damage pictures, loss assessment server 160may create a repair cost range.

After extracting the repair cost data from each of the historical lossassessment matrices and determining the repair cost range, lossassessment server 160 may incorporate the extracted repair cost datainto the fifth category occupying the fifth row and/or column of theloss assessment matrix corresponding to the loss assessment profileassociated with the user. The incorporated repair data may comprise theadjusted repair costs to account for inflation, the applicability ofusing an interchangeable part and the costs associated therein, and thecosts associated with installing the interchangeable part.

Upon incorporating the extracted repair data from the historical lossassessment matrix into the loss assessment matrix corresponding to theloss assessment profile of the user, loss assessment server 160 may thendetermine the accompanying insurance changes associated with filing aclaim to cover the vehicle repair costs. In one example, the lossassessment server 160 may determine the accompanying insurance changesassociated with filing a claim to cover the vehicle repair costs basedupon an analysis of the historical loss assessment profiles sent byhistorical data source server 150 according to the second comparison.During the analysis, loss assessment server 160 may calculate aninsurance premium percentage increase for the historical loss assessmentprofile of the second comparison with the highest confidence rating.Next, loss assessment server 160 may calculate an average insurancepremium increase based on the insurance premium data included in each ofthe historical loss assessment profiles provided by historical datasource server 150. After determining the range of accompanying ofinsurance policy changes associated with filing a claim to cover thevehicle repair costs, loss assessment server 160 may incorporate thedetermined range of accompanying insurance policy changes into the fifthcategory occupying the fifth row and/or column of the loss assessmentmatrix corresponding to the loss assessment profile associated with theuser.

Responsive to determining the repair costs and accompanying insurancepolicy changes, loss assessment server 160 may provide the determinedrepair cost range and the range of accompanying insurance policy changesto the user. Loss assessment server 160 may transmit the determinedrepair costs and the accompanying insurance policy changes to the uservia email and/or text message to the email address and/or the phonenumber provided by the user at step 404 through contact informationscreen 608. Additionally and/or alternatively, loss assessment server160 may be configured to transmit the determined repair costs and theaccompanying insurance policy changes to the user via a pre-FNOL lossassessment application operating on mobile device 120 of the user and/ora pre-FNOL loss assessment web application being accessed by an internetbrowser application operating on mobile device 120.

In instances in which loss assessment server 160 transmits thedetermined repair costs and the accompanying insurance policy changes tothe user via a pre-FNOL loss assessment application and/or a pre-FNOLloss assessment web application, the user may be presented with lossassessment completion screen 610 shown in FIG. 6B. The loss assessmentcompletion screen 610 may include repair cost range field 610A, repairtime range field 610B, premium impact range field 610C, “Save for Later”button 610D, and “File a Claim” button 610E.

The repair cost field 610A may include the determined repair cost rangeof the vehicle, the user's deducible, and the claim payment range (e.g.,the numerical difference between the upper and lower bounds of the costof repair range and the deductible) if a claim were to be filed. Inregards to the user's deductible, depending on whether or not the userpreviously provided login information associated with an insurancepolicy account of the user, the deductible may be a filled entry or thedeductible may be a fillable entry as shown in loss assessmentcompletion screen 610. For example, in the event that the user has notpreviously provided insurance account login information to pre-FNOLsystem 140, the user may be able and/or required to type in theirdeducible into the deductible area of repair cost field 610A.Alternatively, in instances in which the user has previously providedinsurance account login information to pre-FNOL system 140, the lossassessment server 160 may embed the deductible associated with theuser's insurance account into the repair cost field 610A.

In instances in which the user has not previously provided insuranceaccount login information to pre-FNOL system 140, the loss assessmentserver 160 may prompt the user to provide insurance account logininformation and/or to enter their deductible before calculating theclaim payment amount. As will be discussed in further detail below, theuser may be required to provide login information associated with theirinsurance account in order to be able to file a claim to cover thedetermined repairs costs.

The repair time range field 610B may include an estimated repaircompletion time range and a user-selectable “Find a Repair Shop” option.The estimated repair completion time range may be determined by lossassessment server 160 by extracting the completed repair time from thehistorical loss assessment matrices used in determining the repair costrange for the vehicle. In some instances, the estimated repaircompletion time may be dependent on the user's selection of a repairshop under the “Find a Repair Shop” option.

The “Find a Repair Shop” option may be a user-selectable option that,when selected, causes loss assessment server 160 to transmit the user'sloss assessment profile to repair clearinghouse server 170. Upon receiptof the user's loss assessment profile, repair clearinghouse server 170may extract geographical location information corresponding to the userand may generate a map through the pre-FNOL loss assessment applicationoperating on mobile device 120 of the user and/or a pre-FNOL lossassessment web application being accessed by an internet browserapplication operating on mobile device 120. The geographical locationassociated with the mobile device 120 of the user may be used by repairclearinghouse server 170 to localize the map corresponding to the user'sgeographical location. Additionally, repair clearinghouse server 170 mayrender one or more pins on the map corresponding to repair shops in theuser's immediate area based on the user's geographical location. Each ofthe pins associated with a particular repair shop may be auser-selectable pin. Once selected, repair clearinghouse server 170 maygenerate a repair shop specific screen on the pre-FNOL loss assessmentapplication and/or the pre-FNOL loss assessment web application. Therepair shop specific screen may provide data about the repair shop suchas an address, telephone number, pictures of the repair shop, picturesof repair shop employees, types of services performed by the repairshop, and the like. Furthermore, the repair shop specific screen maydisplay a rating and comment section wherein patrons of the repair shopmay provide feedback and a repair shop availability schedule. Throughthe repair shop availability schedule, a user may be able to see therepair shop's availability, forecast a repair completion time for thetype of repairs needed, and schedule a repair with the repair shop.

In some instances, the “Find a Repair Shop” option may be auser-selectable option that, when selected, causes repair clearinghouseserver 170 to generate a sortable list through the pre-FNOL lossassessment application operating on mobile device 120 of the user and/ora pre-FNOL loss assessment web application being accessed by an internetbrowser application operating on mobile device 120. The sortable listmay display each of the repair shops within the geographical locationassociated with the mobile device 120 of the user, starting with thenearest repair shop to the geographical location associated with themobile device 120 and terminating with the repair shop furthest from thegeographical location associated with the mobile device 120. The user ofmobile device 120 may be able to sort the repair shop data comprisedwithin the sortable list based on factors such as highest repairranking, nearest location, repair color availability, and the like. Insome instances, the user may be able to toggle between the map interfaceand the sortable list interface.

The premium impact range field 610C may include insurance policy updateinformation that a user may expect responsive to filing a claim to coverthe determined repair costs. In particular, the premium impact field610C may include the user's current six month total premium cost and theexpected rate increase range of the insurance premium. The calculationof the expected rate increase range of the insurance premium may dependon whether or not the user previously provided login informationassociated with an insurance policy account of the user. For example, inthe event that the user has not previously provided insurance accountlogin information to pre-FNOL system 140, the user may be able and/orrequired to provide login information associated with an insuranceaccount covering the damaged vehicle in order to receive the premiumincrease range calculations. Alternatively, the user may be able toenter their current six month premium cost information into field 610Cand loss assessment server 160 may be able to calculate the six monthpremium changes based on the user entered six month premium costinformation.

Additionally, in the premium impact field 610C, there may be aselectable “Learn More” option that the user may be able to select inorder to receive detailed information regarding the cost increases tothe user's insurance premium. After user selection of the “Learn More”option, loss assessment server 160 may provide the user with detailedinformation about the user's insurance policy and the cost increases tothe user's insurance premium. In some instances, loss assessment server160 may provide the contact information of the user's insurance agent sothat the user may discuss cost increases to the user's insurance premiumassociated with filing a claim.

At the bottom of loss assessment completion screen 610 there may be a“Save for Later” user-selectable button 610D and a “File a Claim”user-selectable button 610E. Responsive to a user selection of the “Savefor Later” button 610D, loss assessment server 160 store the informationshown in fields 610A, 610B, and 610C for later review by the user.Additionally, loss assessment server 160 may indicate a time period inwhich the captured repair cost information and accompanying insurancepolicy change information will be held. The loss assessment server 160may further indicate to the user that after expiration of the timeperiod, the captured repair cost information and accompanying insurancepolicy change information may change. At step 408, responsive to a userselection of the “File a Claim” button 610E, loss assessment server 160may redirect the user detailed damage description screen 508 of FIG. 5Band require the user to enter detailed information about the damages tothe user's vehicle.

In some instances, each of loss assessment completion screens 510, asshown in FIG. 5C, and 610, as shown in FIG. 6B, may further include a“Do Not File Claim” user-selectable button. FIG. 7 describes a pre-FNOLonline advisor method performed by pre-FNOL system 140 responsive toreceiving a user selection of the “Do Not File Claim” button.

At step 702, responsive to a user selection of the “Do Not File Claim”button, loss assessment server 160 may provide a pop-up screen on eitherof loss assessment completion screens 510 and 610. The pop-up screen mayinclude a prompt inquiring whether or not the user would like assistancein facilitating repair of the damages to the vehicle. Additionally, thepop-up screen may include “Yes,” “No,” and “Save for Later”user-selectable buttons. In instances in which the user selects the“Save for Later” button, loss assessment server 160 may performprocesses similar to those described above in regards to a userselection of either “Save for Later” buttons 510D or 610D. In instancesin which the user selects the “No” button, loss assessment server 160may save the user's loss assessment profile and transmit the user's lossassessment profile to historical data source server 150. Upon receipt,historical data source server 150 may store the user's loss assessmentprofile in historical data source database 152. Thus, the lossassessment profile created during the pre-FNOL loss assessment methodmay be used as a historical loss assessment profile by pre-FNOL system140 in a manner similar to that of the historical loss assessmentprofiles described above.

At step 704, loss assessment server 160 may receive a user selection ofthe “Yes” button and may proceed to step 706. Responsive to a userselection of the “Yes” button, loss assessment server 160 may transmitthe loss assessment profile associated with the user to repairclearinghouse server 170. At step 706, upon receipt of the user's lossassessment profile, repair clearinghouse server 170 may extractgeographical location data associated with the user from the user's lossassessment profile and may generate a map and/or sortable list of repairshops corresponding to the geographical location of the user through thepre-FNOL loss assessment application operating on mobile device 120 ofthe user and/or a pre-FNOL loss assessment web application beingaccessed by an internet browser application operating on mobile device120. The geographical location associated with the mobile device 120 ofthe user may be used by repair clearinghouse server 170 to localize themap and/or sortable corresponding to the user's geographical location.Additionally, repair clearinghouse server 170 may render one or morepins on the map corresponding to repair shops in the user's immediatearea based on the user's geographical location. Each of the pinsassociated with a particular repair shop may be a user-selectable pin.Once selected, repair clearinghouse server 170 may generate a repairshop specific screen on the pre-FNOL loss assessment application and/orthe pre-FNOL loss assessment web application. The repair shop specificscreen may provide data about the repair shop such as an address,telephone number, pictures of the repair shop, pictures of repair shopemployees, types of services performed by the repair shop, and the like.Furthermore, the repair shop specific screen may display a rating andcomment section wherein patrons of the repair shop may provide feedbackand a repair shop availability schedule. Through the repair shopavailability schedule, a user may be able to see the repair shop'savailability, forecast a repair completion time for the type of repairsneeded, and schedule a repair with the repair shop.

In some instances, each of the repair shops may be required to chargethe user no more than the fixed bid amount determined during the highaccuracy pre-FNOL loss assessment or the upper-bound bid amountdetermined during the low accuracy pre-FNOL loss assessment.Accordingly, the user may select a repair shop based on the rating ofthe repair shop, the location of the repair shop, and/or the type ofrepairs performed at the repair shop. At step 708, the repairclearinghouse server 170 may receive a user selection of a particularrepair shop at which to have the repairs performed. In some instances,the user selection of the repair shop may further entail a time at whichto have the repairs performed.

Alternatively, upon receipt of the user's loss assessment profile,repair clearinghouse server 170 may extract geographical location dataassociated with the user from the user's loss assessment profile and maygenerate a repair clearinghouse auction block associated with the userand corresponding to the geographical location of the user. Ingenerating the repair clearinghouse auction block, repair clearinghouseserver 170 initially request user permission prior to generating theauction block. After receiving the user's permission, repairclearinghouse server 170 may query the user as to a location range inwhich the auction block will become accessible to repair shops in thegeographical vicinity of the user. For example, the query to the usermay include a dropdown list including a plurality of radial distances(e.g., 10 miles, 25 miles, 50 miles, etc.) in which repair shops may beable to participate in the auction block. In some instances, the usermay also be prompted to provide a zip code and/or address from which theradial distance the radial distance may be marked an a time period inwhich the auction block will remain open (e.g., 1 day, 3 days, 5 days,etc.).

In response to receiving a radial distance from the user, the repairclearinghouse sever 170 may activate a repair clearinghouse auctionblock associated with the user in which repair shops inside of theradial distance specified by the user may be able to place repair bidson the cost of repairing the damages to the vehicle of the user. Ingenerating the repair clearinghouse auction block associated with theuser, repair clearinghouse server 170 may associate informationcorresponding to the accident to the user's auction block. For example,the auction block may include vehicle operational data, responses topreliminary questions regarding an accident, user vehicle selectioninformation (or vehicle profile information), detailed damageinformation (or general damage information) and pictures, and the like.Based on the provided information, repair shops within theuser-specified vicinity may be able to place bids corresponding to thecost of repairing the vehicle. In some instances, the repair costdetermined by pre-FNOL system 140 through the high accuracy pre-FNOLloss assessment may serve as an upper bound that may not be surpassed inthe repair cost bids provided by the repair shops. Similarly, theupper-bound repair cost determined by the pre-FNOL system 140 throughthe low accuracy pre-FNOL loss assessment may serve as an upper boundthat may not be surpasses in the repair cost bids provided by the repairshops.

Repair shops within the user-specified distance may be able to providerepair bids for repairing the damages to the user's vehicle. In someinstances, the repair bids may include an itemized list of the repairsto be performed and the corresponding cost of each of the repairs to beperformed. The user may be able to view the repair bids provided by therepair shops in real time. In some instances, the user may be requiredto wait until the specified auction block time period expires beforeaccepting a repair bid. In other instances, the user may be able toterminate the auction block at any time by selecting a repair bid orwithout selecting a repair bid. Additionally, the user may be able toselect from any of the bids placed to reach a repair agreement. Forexample, in the event that the user receives three bids, the user may beable to select any of the three bids. In response to selecting a bid,the user and the repair shop may enter into a contractual agreement forrepairs and the repair costs specified by the selected bid.

After the user selection of a repair shop at which to have the repairsperformed, in some instances, repair clearinghouse server 170 maygenerate a user provide the user with a sortable list and/or map of towtruck companies proximate to the geographical location associated withthe mobile device 120 of the user. The presentation of the sortable listand/or map of tow truck companies and the functionality related thereinmay be similar to that described above in regards to the repair shops.Furthermore, repair clearinghouse sever 170 may also provide the userwith a sortable list and/or map of rental car agencies proximate to theuser's geographical location. In some instances, the repairclearinghouse server 170 may enable the user to populate the sortablelist and/or map with both rental car agencies and tow truck companiesproximate to the user. The presentation of the sortable list and/or mapof rental car agencies and the functionality related therein may besimilar to that described above in regards to the user selection of therepair shops.

In either instance, at step 710, responsive to the user selection of arepair shop and commencement of repairs at the repair shop, repairclearinghouse server 170 may provide periodic notifications to the userthrough the pre-FNOL loss assessment application operating on mobiledevice 120 of the user and/or a pre-FNOL loss assessment web applicationbeing accessed by an internet browser application operating on mobiledevice 120. The notifications may comprise a repair progress bar, a listof repairs completed, a list of upcoming repairs, and a time associatedwith the upcoming repairs.

At step 712, upon completion of the repairs to the user's vehicle,repair clearinghouse server 170 may provide a notification to the userthat the repairs have been completed. Additionally, repair clearinghouseserver 170 may update the loss assessment profile of the user with thefinalized repairs performed on the vehicle, the time taken to performthe repairs, and the costs associated with the repairs. After updatingthe loss assessment profile, repair clearinghouse server 170 maytransmit the updated loss assessment profile to historical data sourceserver 150. Upon receipt of the loss assessment profile, historical datasource server 150 may store the loss assessment profile in historicaldata source database 154 and the loss assessment profile may serve as ahistorical loss assessment profile in the manner described herein.

FIG. 10 illustrates a block diagram of a computing device 1001 in apre-FNOL loss assessment system 1000 that may be used according to oneor more illustrative embodiments of the disclosure. The computing device1001 may have a processor 1003 for controlling overall operation of thecomputing device 1001 and its associated components, including RAM 1005,ROM 1007, input/output module 1009, and memory unit 1015. The computingdevice 1001, along with one or more additional devices (e.g., terminals1041, 1051) may correspond to any of multiple systems or devices, suchas close call detection devices or systems, configured as describedherein for receiving data from various sources, populating a rollingshort term logical table with the received data, and eliciting aparticular vehicular response based on the populated data itemsexceeding near short term (e.g., five seconds to five minutes)association thresholds.

Input/Output (I/O) module 1009 may include a microphone, keypad, touchscreen, and/or stylus through which a user of the computing device 1001may provide input, and may also include one or more of a speaker forproviding audio input/output and a video display device for providingtextual, audiovisual and/or graphical output. Software may be storedwithin memory unit 1015 and/or other storage to provide instructions toprocessor 1003 for enabling device 1001 to perform various functions.For example, memory unit 1015 may store software used by the device1001, such as an operating system 1017, application programs 1019, andan associated internal database 1021. The memory unit 1015 includes oneor more of volatile and/or non-volatile computer memory to storecomputer-executable instructions, data, and/or other information.Processor 1003 and its associated components may allow the computingdevice 1001 to execute a series of computer-readable instructions toperform the pre-FNOL loss assessment and online advisor methodsdescribed herein.

The computing device 1001 may operate in a networked environment 1000supporting connections to one or more remote computers, such asterminals/devices 1041 and 1051. Close call detection device 1001, andrelated terminals/devices 1041 and 1051, may include devices installedin vehicles, mobile devices that may travel within vehicles, or devicesoutside of vehicles that are configured to receive and process vehicleand other sensor data. Thus, the computing device 1001 andterminals/devices 1041 and 1051 may each include personal computers(e.g., laptop, desktop, or tablet computers), servers (e.g., webservers, database servers), vehicle-based devices (e.g., on-boardvehicle computers, short-range vehicle communication systems, sensorsand telematics devices), or mobile communication devices (e.g., mobilephones, portable computing devices, and the like), and may include someor all of the elements described above with respect to the computingdevice 1001. The network connections depicted in FIG. 10 include a localarea network (LAN) 1025 and a wide area network (WAN) 1029, and awireless telecommunications network 1033, but may also include othernetworks. When used in a LAN networking environment, the computingdevice 1001 may be connected to the LAN 1025 through a network interfaceor adapter 1023. When used in a WAN networking environment, the device1001 may include a modem 1027 or other means for establishingcommunications over the WAN 1029, such as network 1031 (e.g., theInternet). When used in a wireless telecommunications network 1033, thedevice 1001 may include one or more transceivers, digital signalprocessors, and additional circuitry and software for communicating withwireless computing devices 1041 (e.g., mobile phones, short-rangevehicle communication systems, vehicle sensing and telematics devices)via one or more network devices 1035 (e.g., base transceiver stations)in the wireless network 1033.

It will be appreciated that the network connections shown areillustrative and other means of establishing a communications linkbetween the computers may be used. The existence of any of variousnetwork protocols such as TCP/IP, Ethernet, FTP, HTTP and the like, andof various wireless communication technologies such as GSM, CDMA, Wi-Fi,and WiMAX, is presumed, and the various computing devices andmulti-dimensional risk score generation system components describedherein may be configured to communicate using any of these networkprotocols or technologies.

Additionally, one or more application programs 1019 used by thecomputing device 1001 may include computer executable instructions forreceiving data and performing other related functions as describedherein.

As will be appreciated by one of skill in the art, the various aspectsdescribed herein may be embodied as a method, a computer system, or acomputer program product. Accordingly, those aspects may take the formof an entirely hardware embodiment, an entirely software embodiment oran embodiment combining software and hardware aspects. Furthermore, suchaspects may take the form of a computer program product stored by one ormore computer-readable storage media having computer-readable programcode, or instructions, embodied in or on the storage media. Any suitablecomputer readable storage media may be utilized, including hard disks,CD-ROMs, optical storage devices, magnetic storage devices, and/or anycombination thereof. In addition, various signals representing data orevents as described herein may be transferred between a source and adestination in the form of electromagnetic waves traveling throughsignal-conducting media such as metal wires, optical fibers, and/orwireless transmission media (e.g., air and/or space).

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

What is claimed is:
 1. A method comprising: detecting, by a firstcomputing device, that a vehicle has been involved in an accident;activating a camera of a mobile device; generating, on a display of themobile device, a semi-translucent overlay corresponding to a first areaof the vehicle damaged in the accident; causing the mobile device tocapture, with the activated camera, one or more pictures of the vehicledamaged in the accident and corresponding to the semi-translucentoverlay; discarding image data outside of an outer boundary of thesemi-translucent overlay corresponding to the first area of the vehicledamaged in the accident; and calculating, based on the one or morepictures of the first area of the vehicle damaged in the accident,repair costs for the vehicle damaged in the accident and expectedinsurance policy premium changes if an insurance claim is filed to coverthe calculated repair costs.
 2. The method of claim 1, wherein causingthe mobile device to capture the one or more pictures of the first areaof the vehicle damaged in the accident comprises causing the mobiledevice to capture image data corresponding to an entire area of thedisplay of the mobile device, wherein discarding the image data outsideof the semi-translucent overlay corresponding to the first area of thevehicle damaged in the accident comprises discarding portions of asecond area of the vehicle not included in the first area, and whereinthe method further comprises storing remaining, non-discarded imagedata, the stored image data is smaller in size than the captured imagedata.
 3. The method of claim 1, further comprising receiving vehicleoperation sensor data from one or more sensors of the mobile device,wherein the one or more sensors collect the vehicle operation sensordata during the accident.
 4. The method of claim 3, further comprisingproviding, to emergency personnel, an alert that the accident hasoccurred, wherein the alert includes the vehicle operation sensor data.5. The method of claim 1, further comprising responsive to receiving arequest to file the insurance claim, further applying the expectedinsurance policy premium changes to an insurance policy associated witha driver of the vehicle.
 6. The method of claim 1, wherein a second areaof the vehicle comprises a driver side of the vehicle, a passenger sideof the vehicle, a front of the vehicle, or a rear of the vehicle, andwherein the first area of the vehicle comprises a tire, a door, a tirewell, a headlight, hood, a bumper, a windshield, or a taillight.
 7. Themethod of claim 1, further comprising: comparing the one or morepictures of the first area of the vehicle to one or more stored images;and providing, to the mobile device and based on determining that theone or more pictures of the first area of the vehicle do not correspondto any of the one or more stored images, a notification to re-capture animage of the first area of the vehicle damaged in the accident.
 8. Anapparatus comprising: a processor; and memory storing computer-readableinstructions that, when executed by the processor, cause the apparatusto: detect that a vehicle has been involved in an accident; activate acamera of a mobile device; generate, on a display of the mobile device,a semi-translucent overlay corresponding to a first area of the vehicledamaged in the accident; cause the mobile device to capture, with theactivated camera, one or more pictures of the vehicle damaged in theaccident and corresponding to the semi-translucent overlay; discardimage data outside of an outer boundary of the semi-translucent overlaycorresponding to the first area of the vehicle damaged in the accident;and calculate, based on the one or more pictures of the first area ofthe vehicle damaged in the accident, repair costs for the vehicledamaged in the accident and expected insurance policy premium changes ifan insurance claim is filed to cover the calculated repair costs.
 9. Theapparatus of claim 8, wherein memory stores further computer-readableinstructions that, when executed by the processor, cause the apparatusto: generate, on the display of the mobile device, a secondsemi-translucent overlay corresponding to a second area of the vehicledamaged in the accident; and cause the mobile device to capture, withthe activated camera, one or more pictures of the second area of thevehicle damaged in the accident, wherein an outer boundary of the one ormore pictures of the second area of the vehicle damaged in the accidenttraces the second semi-translucent overlay.
 10. The apparatus of claim8, wherein a second area of the vehicle comprises a driver side of thevehicle, a passenger side of the vehicle, a front of the vehicle, or arear of the vehicle, and wherein the first area of the vehicle comprisesa tire, a door, a tire well, a headlight, hood, a bumper, a windshield,or a taillight.
 11. The apparatus of claim 8, wherein memory storesfurther computer-readable instructions that, when executed by theprocessor, cause the apparatus to: compare the one or more pictures ofthe first area of the vehicle to one or more stored images; and provide,to the mobile device and based on determining that the one or morepictures of the first area of the vehicle do not correspond to any ofthe one or more stored images, a notification to re-capture an image ofthe first area of the vehicle damaged in the accident.
 12. The apparatusof claim 8, wherein the memory stores further computer-readableinstructions that, when executed by the processor, cause the apparatusto: receive vehicle operation sensor data from one or more sensors ofthe mobile device; and receive additional vehicle operation sensor datafrom one or more sensors associated with the vehicle or one or moresensors associated with a telematics device associated with the vehicle.13. The apparatus of claim 12, wherein the memory stores furthercomputer-readable instructions that, when executed by the processor,cause the apparatus to provide, to emergency personnel, an alert thatthe accident has occurred, wherein the alert includes the vehicleoperation sensor data.
 14. The apparatus of claim 12, wherein thevehicle operation sensor data includes at least an indication of airbagdeployment.
 15. A computing system, comprising: at least one processor;and at least one memory storing computer-readable instructions that,when executed by the at least one processor, cause the computing systemto: detect that a vehicle has been involved in an accident; activate acamera of a mobile device; generate, on a display of the mobile device,a semi-translucent overlay corresponding to a first area of the vehicledamaged in the accident; cause the mobile device to capture, with theactivated camera, one or more pictures of the vehicle damaged in theaccident and corresponding to the semi-translucent overlay; discardimage data outside of an outer boundary of the semi-translucent overlaycorresponding to the first area of the vehicle damaged in the accident;and calculate, based on the one or more pictures of the first area ofthe vehicle damaged in the accident, repair costs for the vehicledamaged in the accident and expected insurance policy premium changes ifan insurance claim is filed to cover the calculated repair costs. 16.The computing system of claim 15, wherein the memory stores furthercomputer-readable instructions that, when executed by the at least oneprocessor, cause the computing system to: cause the mobile device tocapture the one or more pictures the vehicle damaged in the accident bycausing the mobile device to capture image data corresponding to anentire area of the display of the mobile device; discard the image dataoutside of the semi-translucent overlay corresponding to the first areaof the vehicle damaged in the accident by discarding portions of asecond area of the vehicle not included in the first area; and storeremaining, non-discarded image data, wherein the stored image data issmaller in size than the captured image data.
 17. The computing systemof claim 15, wherein the at least one memory stores furthercomputer-readable instructions that, when executed by the at least oneprocessor, cause the computing system to: compare the one or morepictures of the first area of the vehicle to one or more stored images;and provide, to the mobile device and based on determining that the oneor more pictures of the first area of the vehicle do not correspond toany of the one or more stored images, a notification to re-capture animage of the first area of the vehicle damaged in the accident.
 18. Thecomputing system of claim 15, wherein a second area of the vehiclecomprises a driver side of the vehicle, a passenger side of the vehicle,a front of the vehicle, or a rear of the vehicle, and wherein the firstarea of the vehicle comprises a tire, a door, a tire well, a headlight,hood, a bumper, a windshield, or a taillight.
 19. The computing systemof claim 15, wherein the at least one memory stores furthercomputer-readable instructions that, when executed by the at least oneprocessor, cause the computing system to: receive vehicle operationsensor data from one or more sensors of the mobile device, wherein thevehicle operation sensor data includes at least an indication of airbagdeployment; and receive additional vehicle operation sensor data fromone or more sensors associated with the vehicle or one or more sensorsassociated with a telematics device associated with the vehicle.
 20. Thecomputing system of claim 19, wherein the at least one memory storesfurther computer-readable instructions that, when executed by the atleast one processor, cause the computing system to provide, to emergencypersonnel, an alert that the accident has occurred, wherein the alertincludes the vehicle operation sensor data.